Add a proper title and popup attributes to page-options button.
Make recommended card's add-on names headings.
Give the HTML pane a title so it reads better in screen readers.
Always include a label for the search box.
Clarify the label on the extension enable checkbox.
Differential Revision: https://phabricator.services.mozilla.com/D54874
--HG--
extra : moz-landing-system : lando
This change allows for background scripts from WebExtensions to run in the FxR on PC chrome window. In this scenario, the promise ExtensionParent.browserStartupPromise is never fulfilled because it depends on the notification sessionstore-windows-restored, which doesn't occur because the FxR window does not participate in SessionStore.
To address this issue, browserStartupPromise is now a race between the original notification and a new one, extensions-late-startup, which is fired from fxrui.js.
Differential Revision: https://phabricator.services.mozilla.com/D55058
--HG--
extra : moz-landing-system : lando
Initially this was going to be a simple cleanup: Remove some useless namespaces
here and there and so on, remove `using` statements from the header and so on.
But unfortunately, DOMIntersectionObserver.h (which is included in Element.h,
unnecessarily) ended up exposing `Element` unnamespaced to a lot of code, so I
had to fix that.
Differential Revision: https://phabricator.services.mozilla.com/D55316
--HG--
extra : moz-landing-system : lando
This merges the previously two overlapping lists into one, with different classes to make obtaining the results easier.
As a side effect, preference based MozParams could now also be specified with a purpose.
Preference caching/observation to be added in the next changeset.
Differential Revision: https://phabricator.services.mozilla.com/D54898
--HG--
extra : moz-landing-system : lando
Bug 587780 originally added MozParam's purpose argument, at the time the default fallback was an empty string. This meant that to match only the default, purpose had to be defined as an empty string. In bug 1181645, the default purpose was changed to fallback to the string "searchbar", obsoleting the need for handling purpose as an empty string. However, the handling wasn't removed, making the code more complicated.
Differential Revision: https://phabricator.services.mozilla.com/D54897
--HG--
extra : moz-landing-system : lando
macOS and Windows seem to already have minimum window size limits that
make sense, so this hacks in a minimum size just for Linux GTK and leaves
the others alone.
Differential Revision: https://phabricator.services.mozilla.com/D55152
--HG--
extra : moz-landing-system : lando
From extensive testing, it appears that the test fails (also on TV)
when one of the home pages is opened. This did not happen with
"about:robots". Apparently, a browser window leak can be observed if the
test starts at a homepage and opens another homepage tab in the test.
This patch works around the issue by initializing the window with about:blank.
Differential Revision: https://phabricator.services.mozilla.com/D55108
--HG--
extra : moz-landing-system : lando
This merges the previously two overlapping lists into one, with different classes to make obtaining the results easier.
As a side effect, preference based MozParams could now also be specified with a purpose.
Preference caching/observation to be added in the next changeset.
Differential Revision: https://phabricator.services.mozilla.com/D54898
--HG--
extra : moz-landing-system : lando
Bug 587780 originally added MozParam's purpose argument, at the time the default fallback was an empty string. This meant that to match only the default, purpose had to be defined as an empty string. In bug 1181645, the default purpose was changed to fallback to the string "searchbar", obsoleting the need for handling purpose as an empty string. However, the handling wasn't removed, making the code more complicated.
Differential Revision: https://phabricator.services.mozilla.com/D54897
--HG--
extra : moz-landing-system : lando
By making the final redirect use a cross-origin destination we can exercise the fission code and expose issues.
Differential Revision: https://phabricator.services.mozilla.com/D54454
--HG--
extra : moz-landing-system : lando
This patch uses similar architecture of use counters of main thread for workers.
Which introduces the following format histograms for use counters of workers
USE_COUNTER2_*_DEDICATED_WORKER
USE_COUNTER2_*_SHARED_WORKER
USE_COUNTER2_*_SERVICE_WORKER
And add the following histograms used in conjunction with above use counter histograms
DEDICATED_WORKER_DESTROYED
SHARED_WORKER_DESTROYED
SERVICE_WORKER_DESTROYED
Differential Revision: https://phabricator.services.mozilla.com/D53221
--HG--
rename : dom/base/UseCounters.conf => dom/base/UseCountersWorker.conf
extra : moz-landing-system : lando
This has the effect of reverting changeset 17183959c3a9 but with formatting
changes and other non-functional updates due to changes since the original
implementation was removed.
Differential Revision: https://phabricator.services.mozilla.com/D54790
--HG--
extra : moz-landing-system : lando
Add backend stuff to build sandboxed wasm libraries. (Don't actually update any moz.build files to consume this yet.)
Differential Revision: https://phabricator.services.mozilla.com/D54152
--HG--
extra : moz-landing-system : lando