Converts dom.timeout.enable_budget_timer_throttling from varcache pref to static pref, removes entry from all.js, adds entry to StaticPrefList.yaml. Uses the all.js value and not the value declared in TimeoutManager.cpp. Since this removes the last varcache pref from TimeoutManager::Initialize(), I also removed the Initialize() function and its call in nsGlobalWindowInner.
Differential Revision: https://phabricator.services.mozilla.com/D39455
--HG--
extra : moz-landing-system : lando
Converts dom.timeout.budget_throttling_max_delay varcache pref to static pref, removes entry from all.js, and adds entry to StaticPrefList.yaml
Differential Revision: https://phabricator.services.mozilla.com/D39451
--HG--
extra : moz-landing-system : lando
Converts dom.timeout.foreground_budget_regeneration_rate varcache pref in TimeoutManager.cpp to static pref, removes entry in all.js, adds entry in StaticPrefList.yaml.
Differential Revision: https://phabricator.services.mozilla.com/D39436
--HG--
extra : moz-landing-system : lando
Converts dom.timeout.background_budget_regeneration_rate varcache pref in TimeoutManager.cpp to static pref, removes entry in all.js, adds entry to StaticPrefList.yaml.
Differential Revision: https://phabricator.services.mozilla.com/D39435
--HG--
extra : moz-landing-system : lando
Converts dom.disable_open_click_delay from a VarCache pref in TimeoutManager.cpp to StaticPref, removes all.js entry, and corrects a typo where the value was mentioned in nsGlobalWindowInner.cpp.
Differential Revision: https://phabricator.services.mozilla.com/D39424
--HG--
extra : moz-landing-system : lando
Converts dom.timeout.max_consecutive_callbacks_ms varcache pref in TimeoutManager.cpp to static pref, removes associated variables and all.js entry, and adds entry to StaticPrefList.yaml.
Differential Revision: https://phabricator.services.mozilla.com/D39425
--HG--
extra : moz-landing-system : lando
Converts dom.timeout.throttling_delay in TimeoutManager.cpp from varcache pref to static pref, removes entry in all.js, and adds entry in StaticPrefList.yaml. Favors the all.js value over the declared value in TimeoutManager.cpp.
Differential Revision: https://phabricator.services.mozilla.com/D39426
--HG--
extra : moz-landing-system : lando
Removes dom.min_tracking_timeout_value and dom.min_tracking_background_timeout_value, because they are never used.
Differential Revision: https://phabricator.services.mozilla.com/D39429
--HG--
extra : moz-landing-system : lando
Converts dom.min_background_timeout_value in TimeoutManager.cpp to static pref, removes entry in all.js, adds entry to StaticPrefList.yaml.
Differential Revision: https://phabricator.services.mozilla.com/D39430
--HG--
extra : moz-landing-system : lando
Converts dom.min_timeout_value varcache pref from TimeoutManager::Initialize() to a static pref, and removes its entry and associated constants from TimeoutManager.cpp and all.js
Differential Revision: https://phabricator.services.mozilla.com/D39416
--HG--
extra : moz-landing-system : lando
Bug 1547669 added some things to the top sites API, but it turned out to be not quite what we (the quantumbar team) needed (see bug 1568617). What we need is the list of top sites exactly as it appears on newtab. That list is determined by activity stream, which lives in browser. But the top sites API lives in toolkit.
There was an earlier, now abandoned revision for that bug [1] where it was suggested that top sites be moved to browser. So we should do that.
[1] https://phabricator.services.mozilla.com/D36200
Differential Revision: https://phabricator.services.mozilla.com/D39589
--HG--
rename : toolkit/components/extensions/parent/ext-topSites.js => browser/components/extensions/parent/ext-topSites.js
rename : toolkit/components/extensions/schemas/top_sites.json => browser/components/extensions/schemas/top_sites.json
rename : toolkit/components/extensions/test/xpcshell/test_ext_topSites.js => browser/components/extensions/test/xpcshell/test_ext_topSites.js
extra : moz-landing-system : lando
The previous behaviour of failing unconditionally was performed as, during
shutdown, the channel could become unable to send without worker threads having
a chance to react. This change keeps that behaviour, isolating async message
senders from impending IPC shutdown, while performing expected actor teardown if
the manager actor has already been destroyed, and should no longer send messages.
An alternate behaviour here could be to crash if !Manager()->CanSend(). That
behaviour may be preferable if a sufficient number of callsites don't check the
return value of the `SendPFooConstructor()` method.
Differential Revision: https://phabricator.services.mozilla.com/D39534
--HG--
extra : moz-landing-system : lando
The URL bar was expanding to cover the tab switcher button, meaning that a new tab could not be navigated to after opening.
This is needed so that members of the Gecko media team can replicate an issue in GVE that causes images not to be displayed in Fenix.
Differential Revision: https://phabricator.services.mozilla.com/D39678
--HG--
extra : moz-landing-system : lando
Gecko had a bug where content would be able to see an internal
onunload handler used to handle the case where the page navigates when
script is running. This test ensures that onunload isn't set when
running a script and that changes to addEventListener from content
aren't visible to the harness internal code.
Differential Revision: https://phabricator.services.mozilla.com/D39523
--HG--
extra : moz-landing-system : lando
Internal marionette listeners should neither be visible to content
script, nor have their registation affected by changes made in
content. The evaluate method was breaking these constraints by
creating listeners in a sandbox with Xrays disabled, which is
appropriate to the injected script itself but not to the
harness-internal parts.
Use a different sandbox for the harness code compared to the injected
code, and move away from using onunload to using addEventListener for
the unload handler.
Differential Revision: https://phabricator.services.mozilla.com/D39522
--HG--
extra : moz-landing-system : lando
This change replaces and removes code in VRManager that was refactored into the
new VRShMem class.
Differential Revision: https://phabricator.services.mozilla.com/D36986
--HG--
extra : moz-landing-system : lando
If the contextId parameter is omitted when calling Runtime.evaluate,
the expression will be performed in the context of the currently
inspected page.
Differential Revision: https://phabricator.services.mozilla.com/D36823
--HG--
extra : moz-landing-system : lando
Sometimes we don't have origin like OCSP requests, or a fetch issues from web extension.
We should not send `Origin:`
Spec doesn't specify how to treat other protocol like moz-extension.
IMO we should also prevent sending `Origin:` to keep web-compat.
Differential Revision: https://phabricator.services.mozilla.com/D39595
--HG--
extra : moz-landing-system : lando
asm.js optimized compilation can be disabled by the unavailability of
ion-for-wasm through command line option selection; we must therefore
gate carefully.
Differential Revision: https://phabricator.services.mozilla.com/D38163
--HG--
extra : moz-landing-system : lando
One of the issues with the test-case in this bug is that the page consumes a ton
of CPU due to scroll anchor adjustments being triggered from scroll events,
which in turn cause other scroll events to fire.
This happens in Chrome as well (just scroll to the bottom of the test-case, and
do `addEventListener("scroll", () => console.log("scroll"))` on devtools. But I
think it's worth fixing. This patch fixes it and overall I think it's a slightly
better approach to suppress adjustments than what we're doing.
Differential Revision: https://phabricator.services.mozilla.com/D39339
--HG--
extra : moz-landing-system : lando
We need to update the test since '#tracking-protection-icon-container'
is accessible before the '#identity-box'.
Differential Revision: https://phabricator.services.mozilla.com/D39330
--HG--
extra : moz-landing-system : lando
This patch fixes the issue that the keyboard navigation doesn't work for
the tracking protection icon.
Differential Revision: https://phabricator.services.mozilla.com/D39329
--HG--
extra : moz-landing-system : lando
This is due to an implementation detail of the IonMonkey backend, which stores
call sites bytecode numbers on 29 bits, for packing purposes. The wasm baseline
compiler doesn't have this issue because it stores them on 32 bits. Check it to
avoid an easy browser DOS.
Differential Revision: https://phabricator.services.mozilla.com/D37845
--HG--
extra : moz-landing-system : lando
Geoff Brown
Carolina
Kristen Wright
Andrew Halberstadt
Ryan Hunt
Drew Willcoxon
Nika Layzell
Jon Coppeard
Emily Toop
Thomas Nguyen
James Willcox
Bogdan Tara
Sebastian Hengst
James Graham
thomasmo
Andreas Tolfsen
Kershaw Chang
Belén Albeza
Olli Pettay
Junior Hsu
Lars T Hansen
Tooru Fujisawa
Boris Zbarsky
Emilio Cobos Álvarez
Tim Huang
Mike Conley
Csoregi Natalia
Benjamin Bouvier