We'll always need a URI for DocShellLoadState, and it should only
change is special circumstances. Construct the object with it, and
then follow up in Bug 1515433 for more cleanup.
Differential Revision: https://phabricator.services.mozilla.com/D13490
--HG--
extra : moz-landing-system : lando
Otherwise we risk building up a buffer in the microphone source from when
Start() is run until pulling is enabled. This manifests itself as input latency
to the user.
Differential Revision: https://phabricator.services.mozilla.com/D15194
--HG--
extra : moz-landing-system : lando
All subclasses are now returning NS_OK, so there's no point in keeping nsresult
as the return type.
Differential Revision: https://phabricator.services.mozilla.com/D15193
--HG--
extra : moz-landing-system : lando
These calls have to happen in the parent process to have any effect. I
experimented with making ServiceWorkerCleanUp.jsm do the remoting itself but
that didn't turn out to be worth the effort and it turns out all of the uses
are currently in the parent process anyway.
Differential Revision: https://phabricator.services.mozilla.com/D15160
--HG--
extra : moz-landing-system : lando
This patch adds a toolchain task for building d8 with customized build settings and uses it in jsshell benchmark tests. A customized image with a debian9-base ('custom-v8') is added by this patch as well and is required to build the tool.
Differential Revision: https://phabricator.services.mozilla.com/D14019
--HG--
extra : moz-landing-system : lando
Check whether an input was ever type=password rather than just checking the current type to handle sites which toggle password visibility.
I haven't yet figured out what this code is used for so haven't made a test yet.
Differential Revision: https://phabricator.services.mozilla.com/D15149
--HG--
extra : moz-landing-system : lando
Cache whether an input was ever type=password so consumers can handle sites which toggle password visibility and don't want to save the value of the field.
Differential Revision: https://phabricator.services.mozilla.com/D15145
--HG--
extra : moz-landing-system : lando
Currently we use the regular fallback path for the mask images used by blobs.
This isn't really the best fit and is causing test failures with the current
blob re-coordination patches.
This changes the code to be more FrameLayerBuilder and handles
invalidation of the mask without using FrameLayerBuilder.
Differential Revision: https://phabricator.services.mozilla.com/D14779
--HG--
extra : moz-landing-system : lando
So we do it while we're still handling re-entrant changes for SVG, since SVG can
post change hints from UpdateOverflow().
Differential Revision: https://phabricator.services.mozilla.com/D12102
--HG--
extra : moz-landing-system : lando
The code was trying to implement the getOwnPropertyDescriptor trap in terms of
getPropertyDescriptor, by comparing the "holder" object we found to the object
we did the lookup on. This becomes buggy when wrappers like WindowProxy are involved.
The patch removes this check and calls JS_GetOwnPropertyDescriptor instead of
JS_GetPropertyDescriptor.
Differential Revision: https://phabricator.services.mozilla.com/D15091
--HG--
extra : moz-landing-system : lando
The `privateSession` key would normally allow persisting the Private Browsing
session across OOMs in Activity's Bundle.
We need to do that to avoid storing private, sensible data on disk like we do
with the normal browsing session.
In some cases `privateSession` would contain a lot of data which, along with
other possible concurrent transactions could overflow Binder's buffer which has
a limited fixed size, currently 1Mb.
To avoid this, we will drop `privateSession` from the Bundle if the resulting
size is greater than a _speculative_ size of 300KBs which would mean that in
the case of an OOM all Private Browsing state would be lost.
Bug 1515592 is filed to investigate for a better solution.
Differential Revision: https://phabricator.services.mozilla.com/D15067
--HG--
extra : moz-landing-system : lando
In order to support IA2 live regions with e10s (bug 1322532), text change events sent from the child process to the parent process use sync IPC.
That comes at a slight performance cost: the content process is blocked until the parent returns from sending and handling the event.
However, there is no reason to do this if the event is not for an accessible inside a live region; current clients don't need the sync behaviour outside of live regions.
Differential Revision: https://phabricator.services.mozilla.com/D15183
--HG--
extra : moz-landing-system : lando
This patch slightly speedups origin initialization by having a special column in
the database table for current data usage.
This patch also fixes a problem with length computation of some unicode strings.
Marco Bonardo
WR Updater Bot
Bobby Holley
Dão Gottwald
Michael Kohler
Kyle Machulis
Andreas Pehrson
Iain Ireland
Blake Kaplan
Alex Gaynor
Gregory Mierzwinski
Wes Kocher
Matthew Noorenberghe
Olli Pettay
Jeff Muizelaar
Mark Banner
Emilio Cobos Álvarez
Margareta Eliza Balazs
Jan de Mooij
Petru Lingurar
James Teh
Cameron McCormack
Jan Varga
Narcis Beleuzu
Jason Laster