This fixes a regression from bug 1483228. It started printing a message to
stdout whenever the local state dir was generated. This caused a failure in
these cramtests since they depend on the stdout of the shell process being
identical.
To fix, make sure we trigger state dir creation in the setup script and
redirect to /dev/null.
Differential Revision: https://phabricator.services.mozilla.com/D19155
--HG--
extra : moz-landing-system : lando
Removes INSTALL_LOCALE (@AB_CD@) since it is no longer used
Replaces MOZ_APP_NAME (@MOZ_APP_NAME@) with AppConstants.MOZ_APP_NAME
Replaces IS_WIN, IS_MACOSX, and IS_UNIX with values available from AppConstants.platform
Replaces BIN_SUFFIX with mozinfo.bin_suffix
Differential Revision: https://phabricator.services.mozilla.com/D19104
--HG--
extra : source : bfc4490bedbde79febcb7eb81cf40c68843b24b0
These are copies of the corresponding gcc-based base toolchain tasks,
with FORCE_GCC and the gcc dependency removed.
We also tweak things a little for those builds to actually end up green.
Differential Revision: https://phabricator.services.mozilla.com/D18903
--HG--
extra : moz-landing-system : lando
PresShell::EventHandler::ComputeRootFrameToHandleEvent() computes root frame
to handle event with popup frame and/or capturing content. The former result
can be rewritten with the latter. So, for cleaning it up with early return
style, we need to split it to 2 methods.
Differential Revision: https://phabricator.services.mozilla.com/D18525
--HG--
extra : moz-landing-system : lando
Created the getUpdateDirFile function and replaced various functions for getting files in the update directory.
Change getApplyDirFile and getStageDirFile so they no longer take a second param for whether the file must exist since few callers used it.
Changed waitForUpdateXMLFiles to be an async function since it simplifies the code and it makes this code eslint rule compliant.
Removed unused param from checkFilesAfterUpdateCommon.
Added removeUpdateFiles function for removing files for the mochitest-browser-chrome and mochitest-chrome tests and removed the removeUpdateDirsAndFiles function which never ran on Linux.
Removed test_9999_cleanup.xul since it won't necessarily run for TV tasks.
Differential Revision: https://phabricator.services.mozilla.com/D19117
--HG--
extra : moz-landing-system : lando
Stop all loads that are coming through Docshells that are currently
being destroyed. Keeps earliest check for this condition, removes
later one.
Depends on D17018
Differential Revision: https://phabricator.services.mozilla.com/D17019
--HG--
extra : moz-landing-system : lando
Loading between 2 history entries is mostly a standalone procedure,
and can be extracted to its own method to clean up InternalLoad.
Depends on D17017
Differential Revision: https://phabricator.services.mozilla.com/D17018
--HG--
extra : moz-landing-system : lando
Since targeting has been moved to another method, we don't need to
know the ContentPolicyType until we're in DoURILoad. We can also move
Srcdoc handling to DoURILoad, as all data is passed with the LoadState.
Depends on D17015
Differential Revision: https://phabricator.services.mozilla.com/D17016
--HG--
extra : moz-landing-system : lando
Allow file-write-unlink in ~/Library/Preferences/Macromedia/Flash Player to allow changes made in the Flash Global Settings panel to persist.
Differential Revision: https://phabricator.services.mozilla.com/D19217
--HG--
extra : moz-landing-system : lando
"input" event listener may want to check HTMLInputElement.validationMessage.
However, due to moving "input" event dispatcher from
HTMLInputElement::SetUserInput() to editor, HTMLInputElement::SetValueInternal()
updates it **after** dispatching "input" event.
This patch makes nsContentUtils::DispatchInputEvent() guarantees to update
validationMessage value before dispatching every event. On the other hand,
SetValueInternal() may be called without "input" event dispatchers. Therefore,
it needs to keep updating validationMessage value in such cases.
Differential Revision: https://phabricator.services.mozilla.com/D19126
--HG--
extra : moz-landing-system : lando
* Add a new pref to determine if we should prompt to capture logins in private browsing
* Avoid non-user-directed updates to last-use timestamps for a form submission login in private browsing
Differential Revision: https://phabricator.services.mozilla.com/D18409
--HG--
extra : moz-landing-system : lando
This position ends up being used for source notes in some cases now, meaning that this can
cause breakpoints to be given the wrong position when assigned to a variable. This fixes
that by using the correct token for the position value.
Differential Revision: https://phabricator.services.mozilla.com/D17662
--HG--
extra : moz-landing-system : lando
When we mark call expressions as breakpoints, we want to make it as likely
as possible that the call has its own unique positon. The existing logic
means that it is more likely that the beginning of a call will align
with the start of an expression statement or other debuggable step point.
By using the property-access location, we're less likely to collide.
Thid also adds a new bytecodes that were missed in the original code that
added this position handling logic.
Differential Revision: https://phabricator.services.mozilla.com/D17661
--HG--
extra : moz-landing-system : lando
Making changes to this test is kind of annoying because the count and
the array items need to be kept in sync. This just avoids that.
Differential Revision: https://phabricator.services.mozilla.com/D17660
--HG--
extra : moz-landing-system : lando
This is just a bit of cleanup I'd noticed while writing new implementations of these.
Differential Revision: https://phabricator.services.mozilla.com/D17659
--HG--
extra : moz-landing-system : lando