This patch adds a new context for the performance-new components. It's
eventually the only place where the settings will live, but for now
the components share the settings between the popup, the devtools panel,
and the about:profiling page.
This page uses the base styling that the preferences page uses. The styles
should obey the theming for the browser, and ignore the devtools theming
colors.
Differential Revision: https://phabricator.services.mozilla.com/D55010
--HG--
extra : moz-landing-system : lando
This commit is fairly trivial, but creates the about:profiler page to
start the new about:profiler work.
Differential Revision: https://phabricator.services.mozilla.com/D53729
--HG--
extra : moz-landing-system : lando
This patch adds a new context for the performance-new components. It's
eventually the only place where the settings will live, but for now
the components share the settings between the popup, the devtools panel,
and the about:profiling page.
This page uses the base styling that the preferences page uses. The styles
should obey the theming for the browser, and ignore the devtools theming
colors.
Differential Revision: https://phabricator.services.mozilla.com/D55010
--HG--
extra : moz-landing-system : lando
This commit is fairly trivial, but creates the about:profiler page to
start the new about:profiler work.
Differential Revision: https://phabricator.services.mozilla.com/D53729
--HG--
extra : moz-landing-system : lando
We might as well do this for now to keep the tests passing when modern config is turned on. It doesn't actually matter what order these particular parameters are listed in.
Differential Revision: https://phabricator.services.mozilla.com/D55641
--HG--
extra : moz-landing-system : lando
Icons added after the initial parsing are likely randomly generated to show badges,
thus they are not good for permanent storage, because they are transient and can
potentially flood the store.
Differential Revision: https://phabricator.services.mozilla.com/D55310
--HG--
extra : moz-landing-system : lando
This patch make changes of Gecko infrastrutures to run a fork server
process.
- ForkServerLauncher is a component, which creates a fork server
process at XPCOM startup.
- nsBrowserApp.cpp and related files have been chagned to start a
fork server in a process.
- Logging and nsTraceRefcnt were changed to make it work with the
fork server.
Depends on D46883
Differential Revision: https://phabricator.services.mozilla.com/D46884
--HG--
extra : moz-landing-system : lando
Also increase the min-width for password generation popups so at least en-US doesn't wrap.
Depends on D55742
Differential Revision: https://phabricator.services.mozilla.com/D55743
--HG--
extra : moz-landing-system : lando
Added @rbarker as a reviewer to check if this will work well within GeckoView for FxR / Android.
Added @bzbarsky for test_interfaces.html. -- I'd like to re-land the secure origin requirement for WebVR as part of this patch, as it doesn't help to have UI that can't guarantee the identity of the origin. (This was backed out due to test failures originally, and since been fixed)
Differential Revision: https://phabricator.services.mozilla.com/D45951
--HG--
rename : browser/components/privatebrowsing/test/browser/browser_privatebrowsing_geoprompt.js => browser/components/privatebrowsing/test/browser/browser_privatebrowsing_rememberprompt.js
extra : moz-landing-system : lando
A couple of problems:
* `pickElement` gets the tip's URL (from `UrlbarUtils.getUrlFromResult`). As long as the picked element isn't the help button, we go ahead and use that URL even if the element is not the main button.
* Even after fixing the previous problem, `_on_mousedown` will "select" the tip row itself (not its buttons). If the tip button is already selected (because it's the heuristic for example), the selection goes away at that point.
So we need to ignore tip elements that aren't the buttons.
Differential Revision: https://phabricator.services.mozilla.com/D55758
--HG--
extra : moz-landing-system : lando
Users can opt out of automatic updates. In that case, when an update is available, we need to let the user download and install it and restart the browser. This case isn't covered in the interventions spec, but it's consistent with the intention to give the user a one-click way to continue on their upgrade path, so I think we should handle it.
This patch adds a `browser.experiments.urlbar.installBrowserUpdateAndRestart` function. At first I made it only install the update, and then the extension called our existing `restartBrowser` function once that finished. But it didn't work because `restartBrowser` must be called from a user-input handler, and apparently by awaiting the install function, any code running after the `await` isn't considered to be in the user-input handler.
Differential Revision: https://phabricator.services.mozilla.com/D55608
--HG--
extra : moz-landing-system : lando
Some of these were obvious typos. Others probably reflect once-correct components
that have been combined, split, or otherwise obsoleted; for these I've tried to
use the component associated with the bugs for recent changes to the affected files.
Differential Revision: https://phabricator.services.mozilla.com/D55756
--HG--
extra : moz-landing-system : lando
Gabriel Luong
Mark Striemer
Harry Twyford
Greg Tatum
Shane Caraveo
Ryan VanderMeulen
Noemi Erli
ffxbld
Michael Kaply
Brian Grinstead
Masatoshi Kimura
Mark Banner
Julian Descottes
Marco Bonardo
Kris Maglione
Thinker Li
Matthew Noorenberghe
Razvan Maries
Kearwood Kip Gilbert
Sean Feng
Drew Willcoxon
Ciure Andrei
Florian Quèze
Dorel Luca
Thomas Nguyen
Kevin Jacobs
Nihanth Subramanya
Neil Deakin
Geoff Brown
Liang-Heng Chen
Daniel Varga