This is a necessary change that was done for Fluent access in bug 1573276. In almost all cases,
we want to rely on the principal for making security decisions, but the principal does not
store the original URI in cases where an about: page was sandboxed (it becomes a null principal URI),
and thus we need to use the documentURI here.
Differential Revision: https://phabricator.services.mozilla.com/D47582
--HG--
extra : moz-landing-system : lando
By default, the remote process takes ownership of a shmem when it's sent over ipc.
Using "unsafe" shmem allows any processes to read/write/deallocate such shmem.
Differential Revision: https://phabricator.services.mozilla.com/D47554
--HG--
extra : moz-landing-system : lando
Only useing `mFlagSyncLooping` to check if the current code is in sync event loop is not enough. The crashtest in this patch shows that `mFlagSyncLooping` is set to false in OnStopReequets while we are still in sync event loop.
`mEventDispatchingSuspended` is set to true right before calling `SpinEventLoopUntil` and set to false after, so we should also use it to check if `SpinEventLoopUntil` is finished.
Differential Revision: https://phabricator.services.mozilla.com/D47240
--HG--
extra : moz-landing-system : lando
Skip frequently crashing test on fission (it was already marked as failing).
Differential Revision: https://phabricator.services.mozilla.com/D47694
--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.
Differential Revision: https://phabricator.services.mozilla.com/D47616
--HG--
extra : moz-landing-system : lando
In `MediaEngineWebRTCMicrophoneSource::EvaluateSettings`, on default settings, the `prefs.mChannels` is updated accordingly. However, it is not used for the calculation of the `FlattenedConstraints`. As a result, the channel count is 0, which is converted to 1, and not the actual device channel count as it should. Thus, the `prefs.mChannels` is used in the calculation of the `FlattenedConstraints`.
Differential Revision: https://phabricator.services.mozilla.com/D47453
--HG--
extra : moz-landing-system : lando
With this commit we no longer follow the value's prototype chain when
creating index updates in IndexedDB.
Differential Revision: https://phabricator.services.mozilla.com/D44438
--HG--
extra : moz-landing-system : lando
This patch does the following to support matching a whitelisted URI when
its domain is eTLD+1:
1. add an URIType to indicate whether a URI is generated by
UrlClassifierCommoon::CreatePairwiseWhiteListURI(), which crafts a
whitelist URL like "toplevel.page/?resource=third.party.domain"
2. call LookupCache::GetLookupWhitelistFragments() if URIType is
nsIUrlClassifierFeature::pairwiseWhitelistedURI before initiating
a lookup.
3. implement LookupCache::GetLookupWhitelistFragments() which creates
an additional fragment by removing the leading component of
third.party.domain
Differential Revision: https://phabricator.services.mozilla.com/D47212
--HG--
extra : moz-landing-system : lando
The previous change is wrong because the sender shouldn't send selection change
notification if `IMEContentObserver` does not receive text change notifications
nor selection change notifications.
This patch reverts the change in the if block of previous change and instead
sets `IMEContentObserver::mNeedsToNotifyIMEOfSelectionChange` to `true` if
the sender sends a text change notification. (Note that even if there is
another text change with a mutation event listener, we need to send selection
change notification later so that this must be the right approach.)
Differential Revision: https://phabricator.services.mozilla.com/D47564
--HG--
extra : moz-landing-system : lando
The signatures were updated in the previous patch to hand us the raw,
uncopied buffers. This just adjusts the callsites to match.
Differential Revision: https://phabricator.services.mozilla.com/D34653
--HG--
extra : moz-landing-system : lando
This just splits out the InputBuffer and OutputBuffer helper classes
to make it cleaner for the StartupCache to include them.
Differential Revision: https://phabricator.services.mozilla.com/D34651
--HG--
extra : moz-landing-system : lando
This will not behave exactly the same if we had previously written bad
data for the entry that would fail to decompress. I imagine this is rare
enough, and the consequences are not severe enough, that this should be
fine.
Differential Revision: https://phabricator.services.mozilla.com/D30643
--HG--
extra : moz-landing-system : lando