This value isn't really used, nevertheless it's good to have it to the
right value for documentation reason and consistency.
Differential Revision: https://phabricator.services.mozilla.com/D49643
--HG--
extra : moz-landing-system : lando
This also renames various variables from "settings" to "preferences" to
make it clearer that the values are about actual preferences stored in
the user profile.
Differential Revision: https://phabricator.services.mozilla.com/D49641
--HG--
extra : moz-landing-system : lando
* This patch makes pages with the `OPENER_POLICY_SAME_ORIGIN_EMBEDDER_POLICY_REQUIRE_CORP` policy load into a special `webCOOP+COEP={pageOrigin}` remote type.
* Adds `E10SUtils.WEB_REMOTE_COOP_COEP_TYPE_PREFIX="webCOOP+COEP="`
* When a COOP process switch occurs and the target page doesn't have this policy, we pass a `preferredRemoteType="web"` into `E10SUtils.getRemoteTypeForPrincipal` ensuring that we correctly get a different `remoteType`
* E10SUtils.getRemoteTypeForPrincipal is changed such that `if preferredRemoteType.startsWith(WEB_REMOTE_COOP_COEP_TYPE_PREFIX)` we don't override it with `webIsolated={pageOrigin}`.
* `coop_header.sjs` is changed to also allow setting `Cross-Origin-Embedder-Policy` headers
* `browser_httpCrossOriginOpenerPolicy.js` is changed to test that pages are correctly opened in the correct remoteType process.
Differential Revision: https://phabricator.services.mozilla.com/D48715
--HG--
extra : moz-landing-system : lando
The function used to translate a function how requires a
ModuleTranslationState, which contains state collected after reading early
sections of a wasm module. Currently, this is only used in Cranelift for the
multi-value feature (to read block type signatures), so we can use a dummy
state that's shared across all functions.
Differential Revision: https://phabricator.services.mozilla.com/D49933
--HG--
extra : moz-landing-system : lando
On my (pretty powerful) machine, running binary.js takes 7 seconds before this
patch, 2.5 seconds after the patch. The slow test behaves even worse with
Cranelift, taking up to 20 seconds. Splitting this particular test in its own
test file makes it run in parallel and reduce overall time spent on binary.js.
Differential Revision: https://phabricator.services.mozilla.com/D49926
--HG--
extra : moz-landing-system : lando
Since wasm multi-value is enabled by default (without a shell switch), there
was no way to signal it was disabled in certain configurations, namely
Cranelift.
Instead, assume multi-value is enabled by default and disable it with
Cranelift, and store this information in the CompilerEnvironment so we can use
it when iterating on the wasm binary.
Differential Revision: https://phabricator.services.mozilla.com/D49925
--HG--
extra : moz-landing-system : lando
We can simplify this method by using std::remove_if, which does the shifting down of removed elements for us. We just need to make sure all our wrapper classes support moving assignment.
Differential Revision: https://phabricator.services.mozilla.com/D49769
--HG--
extra : moz-landing-system : lando
Since markers are stored directly into the buffer:
- We don't need to wait for a sampling run to collect them,
- No markers are left uncollected between the last sampling and the time we stop
the profiler.
Differential Revision: https://phabricator.services.mozilla.com/D49233
--HG--
extra : moz-landing-system : lando
`stopProfilerAndGetThreads()` waits until at least one sample appears in the
main thread, before capturing a profile and stopping the profiler.
`stopProfilerNowAndGetThreads()` does not wait; this should be useful in tests
that may not generate any samples (e.g., using the nostacksampling feature).
Differential Revision: https://phabricator.services.mozilla.com/D49232
--HG--
extra : moz-landing-system : lando
Expose the Gecko Profiler feature "nostacksampling" as "No Periodic Sampling".
Differential Revision: https://phabricator.services.mozilla.com/D49231
--HG--
extra : moz-landing-system : lando
There is no behavior change here - these asserts were previously being hit
inside the operator+ of RangedPtr, but this makes them explicit.
Differential Revision: https://phabricator.services.mozilla.com/D49985
--HG--
extra : moz-landing-system : lando
Although many Clients API usages are inherently exclusive (a specific claim
or control request), the execution-ready promise is shared by all requests
to get the state of a client that is not yet execution ready.
Differential Revision: https://phabricator.services.mozilla.com/D49976
--HG--
extra : moz-landing-system : lando
Owing to a lack of test coverage, the changes in bug 1469048 regressed our
de facto privacy/devtools API at nsIServiceWorkerManager.propagateUnregister
to no longer wipe the given registration. The intent of that bug's changes
was to stop the now-moot propagation, but that particular intentional mis-use
of the API was missed.
This patch fixes the problem but maintains the parent-intercept behavior of
only calling ServiceWorkerRegistrar::UnregisterServiceWorker only once.
Differential Revision: https://phabricator.services.mozilla.com/D49996
--HG--
extra : moz-landing-system : lando
Replacing jsbytecode and pcToOffset with BytecodeLocation and BytecodeIterator.
Differential Revision: https://phabricator.services.mozilla.com/D41485
--HG--
extra : moz-landing-system : lando
Replacing uses of `jsbytecode` and `pcToOffset` with `BytecodeLocation` and `BytecodeIterator`
Differential Revision: https://phabricator.services.mozilla.com/D41326
--HG--
extra : moz-landing-system : lando
Post-increment overload operator for BytecodeIterator class matches the operator for pre-increment in BytecodeIterator, meaning the implementation of post-increment is incorrect.
Differential Revision: https://phabricator.services.mozilla.com/D48112
--HG--
extra : moz-landing-system : lando
