In the old setup, a lookup with an nsAString key would implicitly construct an
AtomOrString, which would assign the key to an nsString. This would lead to
copies and heap-allocations if the key was an autostring, which it typically is
when coming from bindings.
This fix improves the performance of the new window-named-property-get.html pref
reftest by about 20-30%, and improves the new getElementById-1.html test by 2-3x.
Differential Revision: https://phabricator.services.mozilla.com/D44015
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
Also, remove an old obsolete preference (getWithPerformance) from test profiles.
Differential Revision: https://phabricator.services.mozilla.com/D40623
--HG--
extra : moz-landing-system : lando
Adds a new pageload test that captures the "pagerendered" event from
PDF.js.
Differential Revision: https://phabricator.services.mozilla.com/D37935
--HG--
extra : moz-landing-system : lando
Adds a new pageload test that captures the "pagerendered" event from
PDF.js.
Differential Revision: https://phabricator.services.mozilla.com/D37935
--HG--
extra : moz-landing-system : lando
Adds a new pageload test that captures the "pagerendered" event from
PDF.js.
Differential Revision: https://phabricator.services.mozilla.com/D37935
--HG--
extra : moz-landing-system : lando
ChromeUtils.import still support a second argument as it used to do
when it was Components.utils.import. But this is deprecated and we should
instead always use the returned value.
Differential Revision: https://phabricator.services.mozilla.com/D37708
--HG--
extra : moz-landing-system : lando
It wasn't working because it was testing inline size == NS_UNCONSTRAINEDSIZE
rather than block size, so it was taking always the reflow path.
The attached test is on par with the vertical-lr / horizontal-tb cases with
this patch, but takes way over 10s without it.
Differential Revision: https://phabricator.services.mozilla.com/D37437
--HG--
extra : moz-landing-system : lando
We now prepend a very large string before the value we
want to autocomplete so we can check it doesn't have too
much impact on the overall autocomplete function.
Differential Revision: https://phabricator.services.mozilla.com/D36573
--HG--
extra : moz-landing-system : lando
On my machine this test takes ~5200 ms with the anonymous content style
caching pref disabled, and ~1000 ms with it enabled.
Differential Revision: https://phabricator.services.mozilla.com/D36139
--HG--
extra : moz-landing-system : lando
On my machine this test takes ~5200 ms with the anonymous content style
caching pref disabled, and ~1000 ms with it enabled.
Differential Revision: https://phabricator.services.mozilla.com/D36139
--HG--
extra : moz-landing-system : lando
This isn't necessary, since it has only 2 static children (the selected tab's content
and the customizable UI), and their visibility is toggled in a single place. We already
toggle .hidden for both - there's no need for a separate deck.
Differential Revision: https://phabricator.services.mozilla.com/D34792
--HG--
extra : moz-landing-system : lando
These are generally:
- Code comments to browser.xhtml
- Testcases, assertions that were mostly using browser.xul as a generic chrome URL
- References to the browser.xul path in tree
Differential Revision: https://phabricator.services.mozilla.com/D33208
This patch introduces a new type of content process, which has a dynamic name.
This type of content process is labeled as `webIsolated=${SITE_ORIGIN}` and is
used within fission-enabled windows.
To enable this, additional information about the fission status of the target
window must be passed into E10SUtils. This was done by updating every call site
manually to pass an extra boolean. A better solution perhaps should be used in
the future.
With this patch enabled, we now perform process switches, but only when
navigating to HTTP URIs. If we navigate to a non-HTTP URI in an iframe with
fission enabled, it will not behave correctly. This must be done in a
follow-up.
Differential Revision: https://phabricator.services.mozilla.com/D29570
--HG--
extra : moz-landing-system : lando