This removes the obsolete backend. Notes on some of the less obvious changes
made as part of this patch:
- some of the gFoo style getters in Blocklist.jsm were only used by the XML
version of the blocklist; I've removed them and tried to remove spurious
settings of those properties in the remaining tests.
- some utility methods (e.g. distribution information getters) were also only
used for the XML version (for the update URL).
- it's no longer necessary to test switching implementations.
- in browser/base/content/test/plugins/, we ran some tests from two manifests
in order to run them with both blocklist backends. The simplest way of
reducing this back down to one was to remove the remote-settings one. If I'd
been more future-oriented when I created the duplication, perhaps I would
have moved the XML version out into a different manifest instead, but I
didn't, so now it looks like we're removing the modern one, whereas really
we're going to be running the modern one as part of the "normal" tests and
we're no longer running the "old" tests.
- removed all mentions I could see of extensions.blocklist.url which is no
longer used for anything.
- per https://bugzilla.mozilla.org/show_bug.cgi?id=1016555#c23, updated
references for the OneCRL timing and how it relates to blocklist updates.
Differential Revision: https://phabricator.services.mozilla.com/D64933
--HG--
extra : moz-landing-system : lando
This prevents the popup to cover the eager evaluation result.
In order for the popup to be able to appear outside of the
toolbox, we pass the useXulWrapper option to the HTMLTooltip.
Differential Revision: https://phabricator.services.mozilla.com/D62431
--HG--
extra : moz-landing-system : lando
Major version number bump for both mozlog and mozcrash + requirements update.
This is very much like the previous mozlog major bump - see bug 1591384.
This patch does not update testing/web-platform/tests/tools/wptrunner/requirements.txt;
I expect that will be automatically updated by the pyup.io bot once mozlog is re-released.
Differential Revision: https://phabricator.services.mozilla.com/D65135
--HG--
extra : moz-landing-system : lando
'fixed' because Talos reports FPS and I'm not sure how to change it.
'30000' because so long as we're over ~3fps, we should get solid perf
data. (and Chrome hits 60fps for me on 10k, but ~30fps at 30k, and we
want room to grow)
Differential Revision: https://phabricator.services.mozilla.com/D63011
--HG--
extra : moz-landing-system : lando
Part 1: Only show Waterfall only for visible rows: IntersectionObserver
collects which rows are off screen as state. New elements register with
the list observer and unregister later. Waterfall column is only
rendered for visible rows and just an empty TD for the rest.
Part 2: Scale Waterfall without transform: Waterfall isn't handled by
CSS variables anymore (expensive styling fix).
Differential Revision: https://phabricator.services.mozilla.com/D58476
--HG--
extra : moz-landing-system : lando
Part 1: Only show Waterfall only for visible rows: IntersectionObserver
collects which rows are off screen as state. New elements register with
the list observer and unregister later. Waterfall column is only
rendered for visible rows and just an empty TD for the rest.
Part 2: Scale Waterfall without transform: Waterfall isn't handled by
CSS variables anymore (expensive styling fix).
Differential Revision: https://phabricator.services.mozilla.com/D58476
--HG--
extra : moz-landing-system : lando
The tests are now using mutation observer to check
when the dom is updated instead.
Differential Revision: https://phabricator.services.mozilla.com/D57499
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset 27cec4c76272 (bug 1601688)
Backed out changeset 9aa05612f10f (bug 1601688)
--HG--
extra : rebase_source : 8be2ada196777716cf7a1a47112033b8d1afd481
The tests are now using mutation observer to check
when the dom is updated instead.
Differential Revision: https://phabricator.services.mozilla.com/D57499
--HG--
extra : moz-landing-system : lando
* talos-powers-content.js has to use `wantUntrusted` to receive untrusted
events from page scripts unless enablePrivilege is used.
* Removed `contentMarker` because it is unused and it depends on
enablePrivilege to call `Services.profiler.AddMarker`.
Differential Revision: https://phabricator.services.mozilla.com/D57240
--HG--
extra : moz-landing-system : lando
While I'm here, I sorted the manifest, in order to match the sorted PGO list, so that it's easier to see when there's a discrepancy.
Differential Revision: https://phabricator.services.mozilla.com/D58968
--HG--
extra : moz-landing-system : lando
In brief, this just includes two out-of-process iframes in the
tresize test page, so that when we are resizing the main window,
we will also be resizing in each of the other fission processes.
The current tresize test is registered at a chrome:// URL, so I
had to make it an http URL to have OOP http iframes, which meant
I had to adjust a bit of the framescriptery to account for this.
Differential Revision: https://phabricator.services.mozilla.com/D55572
--HG--
extra : moz-landing-system : lando
Depends on D49569
We can stop using the exact host:port URL and rely on the proxy for all DAMP calls
Differential Revision: https://phabricator.services.mozilla.com/D53317
--HG--
extra : moz-landing-system : lando
This adds a tp5n-multiproc output directory which contains postprocessed
versions of the tp5n set. They are processed to take iframes with relative
URLs and output absolute URLs with domains similar to their original
domains. This will help us better simulate a real-world case for Fission,
which will split processes based on the ETLD+1 of the domain.
Differential Revision: https://phabricator.services.mozilla.com/D53065
--HG--
extra : moz-landing-system : lando
This will cause us to actually launch a new content process, which
we were previously not doing.
Differential Revision: https://phabricator.services.mozilla.com/D50708
--HG--
extra : moz-landing-system : lando
This will simply allow tests to use alternate domains if they want to ensure
they're getting different processes. This is important for realisitcally
measuring the impact of Fission.
Differential Revision: https://phabricator.services.mozilla.com/D50707
--HG--
extra : moz-landing-system : lando