Bug 1533808 introduced code to intercept DLL methods that the Chromium sandbox had already intercepted. That patch did not store the the pointer to the intercepted function in the trampoline data, as is done when intercepting other methods.
Differential Revision: https://phabricator.services.mozilla.com/D28612
--HG--
extra : moz-landing-system : lando
For TV devices, it is useful to have mouse events automatically
interpreted as touch events. On other devices, such as more desktop-like
Android devices, we want to treat mouse events as mouse events. This patch
makes this behaviour controllable by a pref, but keeps the existing default
behaviour of treating mouse events as touch events.
Differential Revision: https://phabricator.services.mozilla.com/D29188
--HG--
extra : moz-landing-system : lando
Change BrowserTestUtils.waitForCondition to TestUtils.waitForCondition per waitForCondition comment in BrowserTestUtils.
Catch waitForCondition exceptions and let checks in the tests catch the failure when dynamic information is helpful for debugging.
Differential Revision: https://phabricator.services.mozilla.com/D29097
--HG--
extra : moz-landing-system : lando
Renames browser_TelemetryUpdatePing.js to browser_telemetry_updatePing_ready.js so it is consistent with the update test naming scheme.
Changes the test to use runTelemetryUpdateTest instead of runUpdateTest.
Add the test to the BITS manifest so it tests downloading the update using BITS.
Differential Revision: https://phabricator.services.mozilla.com/D29096
--HG--
rename : toolkit/mozapps/update/tests/browser/browser_TelemetryUpdatePing.js => toolkit/mozapps/update/tests/browser/browser_telemetry_updatePing_ready.js
extra : moz-landing-system : lando
swapFrameLoaders relies on frame information, but doesn't ensure it's
up-to-date.
The test for this (test_swapFrameLoaders.xul) is relying right now on one of
flushes from the inner documents to also flush the parent document and thus
ensure there's a frame created.
With the patch for this bug, that flush no longer propagates to the parent
document, and the test fails because we throw in:
https://searchfox.org/mozilla-central/rev/66086345467c69685434dd1c5177b30a7511b1a5/dom/base/nsFrameLoader.cpp#1634
This API could probably be made to work without that requirement, but it's
probably not worth it. For now just flush.
Differential Revision: https://phabricator.services.mozilla.com/D29160
--HG--
extra : moz-landing-system : lando
Apparently introduced by bryner back in 2002, and refactored numerous times without too much scrutiny, this:
- presumably was there for binary components (which are no longer supported)
- or external (add-on) restart-required components (ditto)
- or really any non-builtin components (ditto)
- and would presumably at one point store data somewhere... except that's kinda hard without a profile.
- seems to have never been documented, as far as I can tell.
So let's remove it.
Differential Revision: https://phabricator.services.mozilla.com/D29229
--HG--
extra : moz-landing-system : lando
commonDialog.xul and profileDowngrade.xul both may load early enough
during startup that they don't automatically get customElements.js.
The quick workaround here is just to load it explicitly in those documents.
Differential Revision: https://phabricator.services.mozilla.com/D29235
--HG--
extra : moz-landing-system : lando
The test is marked as perma-fail because there are complications with
getting RDM and WindowSnapshot.js to work together. 4 approaches are
discussed in the test itself, and one is attempted, which perma-fails.
The approach that is attempted is the most likely to be turned into an
unexpected pass in the future, so the test is being added as perma-fail.
Differential Revision: https://phabricator.services.mozilla.com/D28900
--HG--
extra : moz-landing-system : lando
This change was originally added as a drive-by optimization in Bug 1501665.
The early-exit apparently routes around a needed side effect in the case
where resolution is re-set to its current value.
Differential Revision: https://phabricator.services.mozilla.com/D28566
--HG--
extra : moz-landing-system : lando
Before landing the remote agent in Firefox Nightly, we had to disable
remote/test/browser/browser_cdp.js because it caused a permafailure
on debug due to a memory leak. We thought the problem was limited
to this specific test, but over the weekend two more intermittent
leaks were discovered:
* https://bugzilla.mozilla.org/show_bug.cgi?id=1546850
* https://bugzilla.mozilla.org/show_bug.cgi?id=1547303
Until we have had time to investigate and plug the leak, we will
disable all the browser-chrome tests on all debug platforms.
Differential Revision: https://phabricator.services.mozilla.com/D29181
--HG--
extra : moz-landing-system : lando
Refactor several occurences of `setTimeout()` to avoid triggering the `eval()` assertion.
Differential Revision: https://phabricator.services.mozilla.com/D28851
--HG--
extra : moz-landing-system : lando
Moving to non-XPCOM data structures, to help with upcoming transfer to mozglue.
Differential Revision: https://phabricator.services.mozilla.com/D24698
--HG--
extra : moz-landing-system : lando
Moving to non-XPCOM data structures, to help with upcoming transfer to mozglue.
Differential Revision: https://phabricator.services.mozilla.com/D24697
--HG--
extra : moz-landing-system : lando
Some macros would not work if they were used in a context where `namespace
mozilla` is not directly accessible. Fixed by added appropriate `mozilla::`
specifiers.
Differential Revision: https://phabricator.services.mozilla.com/D28028
--HG--
extra : moz-landing-system : lando
David Parks
Ting-Yu Lin
Narcis Beleuzu
Kartikaya Gupta
Andrew McCreight
Robert Strong
Mark Goodwin
Julian Descottes
Shane Caraveo
Henrik Skupin
Brian Hackett
shindli
Emilio Cobos Álvarez
Bas Schouten
Gijs Kruitbosch
Brindusan Cristian
Andrew Swan
Jason Laster
Steve Fink
Brad Werth
Cosmin Sabou
Jeff Muizelaar
Andreas Tolfsen
Jan de Mooij
ffxbld
Jonas Allmann
Gerald Squelart
Florin Strugariu
Cameron McCormack
Gurzau Raul
sotaro
Dorel Luca
longsonr