"here" is a bad click target, giving it a proper name helps everyone.
Depends on D50035
Differential Revision: https://phabricator.services.mozilla.com/D50036
--HG--
extra : moz-landing-system : lando
Like visibility, we rely on pointer-events values inheriting down into
scrollbar part elements. So don't cached NAC styles for scrollbar parts
if we have a non-initial value for pointer-events, and adjust the UA
style sheet rules to ensure it is always inherited.
Differential Revision: https://phabricator.services.mozilla.com/D49359
--HG--
extra : moz-landing-system : lando
This means we only need to call parseXULToFragment a max of once per document
instead of a maximum of once per tab (which in practice isn't any better than
not caching since we only run connectedCallback logic once per tab).
Differential Revision: https://phabricator.services.mozilla.com/D50137
--HG--
extra : moz-landing-system : lando
The idea is to stop directly accessing EnumTypeValues::strings in type-unsafe
ways from consumer code.
Differential Revision: https://phabricator.services.mozilla.com/D49533
--HG--
extra : moz-landing-system : lando
Returning a span ensures that consumers don't try to use this without a length,
but does hide the fact that our string is always null-terminated, at least for
the moment...
Differential Revision: https://phabricator.services.mozilla.com/D49531
--HG--
extra : moz-landing-system : lando
Calling browserLoaded without a |wantLoad| after a call to both addTab and
loadURI may resolve with either of the two loaded urls (usually the first). This
patch updates some callsites to remove any possible non-determinism.
Differential Revision: https://phabricator.services.mozilla.com/D49004
--HG--
extra : moz-landing-system : lando
Since BrowserTestUtils.firstBrowserLoaded now resolves slightly later than it
did before, the STATE_STOP notification is dispatched before we get a chance
to add the progress listener in BrowserTestUtils.browserStopped. We should
create both Promises before waiting for the initial load to finish.
Differential Revision: https://phabricator.services.mozilla.com/D50018
--HG--
extra : moz-landing-system : lando
Adds BrowserTestUtilsChild.jsm to the whitelist, and removes content-utils.js.
The BrowserTestUtils actor now listens for "load" and "DOMContentLoaded" events,
so it gets instantiated earlier than before.
Differential Revision: https://phabricator.services.mozilla.com/D49003
--HG--
extra : moz-landing-system : lando
This also updates the two functions (BrowserTestUtils.firstBrowserLoaded,
browser_broadcastchannel.js#browserFrameLoaded) that rely on the previous
event to use the new one.
Differential Revision: https://phabricator.services.mozilla.com/D49002
--HG--
extra : moz-landing-system : lando
Previously there was a somewhat strange setup where we had both TestResolver
and TestMetadata classes. Both had 'resolve_tests' function and the separation
of concerns between the two were not clear.
With this change, all of the logic that is related to manipulating and
resolving the loaded tests has been moved to the TestResolver class. Also, the
TestMetadata class has been renamed to TestLoader, and it is solely responsible
for loading the metadata (from the build backend).
Future commits will add other types of TestLoaders.
Differential Revision: https://phabricator.services.mozilla.com/D49768
--HG--
extra : moz-landing-system : lando
A minor cleanup. Re-write paths will now automatically be joined to
self.topobjdir.
Depends on D49766
Differential Revision: https://phabricator.services.mozilla.com/D49767
--HG--
extra : moz-landing-system : lando
Similar to the vcs change, the MozbuildObject already has a reader attribute
available. So we can re-use that instead of creating our own.
Depends on D49765
Differential Revision: https://phabricator.services.mozilla.com/D49766
--HG--
extra : moz-landing-system : lando
Encapsulates all the logic around generating and loading the build backend
metadata on the TestMetadata class. Previously the TestResolver would trigger
the generation if necessary, and TestMetadata would load it. Now both
generation and loading happens in TestMetadata.load_tests.
This change also adds some convenience properties to make it easier to query
the loaded data.
Differential Revision: https://phabricator.services.mozilla.com/D49765
--HG--
extra : moz-landing-system : lando
This prevents us from adding the puppeteer tests over and over again. It
follows the wpt example.
Differential Revision: https://phabricator.services.mozilla.com/D49790
--HG--
extra : moz-landing-system : lando
Since TestResolver is a subclass of MozbuildObject, there's no need to create
separate repository object. It already has one.
Depends on D49761
Differential Revision: https://phabricator.services.mozilla.com/D49764
--HG--
extra : moz-landing-system : lando
Most of these tests have been disabled for a long time; they run well
in the current test environment.
This completes my review of skipped Android tests.
Differential Revision: https://phabricator.services.mozilla.com/D49954
--HG--
extra : moz-landing-system : lando
Tom Tung
Jan-Erik Rediger
Jon Coppeard
Kagami Sascha Rosylight
Andrea Marchesini
Cameron McCormack
Boris Zbarsky
Daniel Varga
Punam Dahiya
Kirk Steuber
sotaro
jaril
Jason Laster
Dorel Luca
Alex Touchet
Micah Tigley
Ryan VanderMeulen
Brian Grinstead
Gijs Kruitbosch
Kashav Madan
Botond Ballo
Marco Castelluccio
Jorg K
Andrew Halberstadt
Geoff Brown
Dão Gottwald
Edwin Takahashi