Other methods probably should do the same, but for now this fulfills the test requirement. The rest is (or should be) tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1756661.

Differential Revision: https://phabricator.services.mozilla.com/D153977

Differential Revision: https://phabricator.services.mozilla.com/D153782

Per the Streams spec, other specs that want to implement custom TransformStream should use [GenericTransformStream](https://streams.spec.whatwg.org/#other-specs-ts-wrapping) mixin and store a [new TransformStream](https://streams.spec.whatwg.org/#transformstream-set-up) in a slot. This implements the latter part.

Differential Revision: https://phabricator.services.mozilla.com/D153975

Differential Revision: https://phabricator.services.mozilla.com/D153974

This way SetBackpressureChangePromise can be removed which is only exposed for that function.

Differential Revision: https://phabricator.services.mozilla.com/D153973

It was a part of the initial skeleton code where the getters threw NOT_IMPLEMENTED. The methods are wrong anyway since `.forget()` will unset the fields.

Differential Revision: https://phabricator.services.mozilla.com/D153972

Bug 1779005 - Avoid setting |mLoader| to null if we already start a new PAC load, r=necko-reviewers,valentin

Differential Revision: https://phabricator.services.mozilla.com/D154368

Differential Revision: https://phabricator.services.mozilla.com/D153912

Differential Revision: https://phabricator.services.mozilla.com/D153911

Differential Revision: https://phabricator.services.mozilla.com/D154143

This bug solves the crash that resulted from calling `nsRange::ComparePoint()` with both NAC and non-NAC nodes.
This bug does not solve the root issue, being a range with both NAC and non-NAC content
in context of a <select> element being created in the first place.
See also Bug 1784106.

Differential Revision: https://phabricator.services.mozilla.com/D154365

Differential Revision: https://phabricator.services.mozilla.com/D153758

* Allow MWasmCallBase has reference register: tableIndex renamed to tableIndexOrRef
* Implement call_ref in ion
* Enable call_ref.js test

Differential Revision: https://phabricator.services.mozilla.com/D153678

MANUAL PUSH: Orange fix CLOSED TREE

Bug 1768558 Run new "Fenix-Fission" and "GeckoView-Fission" perf tests on AWFY r=perftest-reviewers,sparky,jmaher

Differential Revision: https://phabricator.services.mozilla.com/D151492

Depends on D154277

Differential Revision: https://phabricator.services.mozilla.com/D154278

Bug 650372 - Use the style-system format hint directly in gfx, instead of mapping to a separate internal enum. r=gfx-reviewers,aosmond,lsalzman

Now that the style system has keywords for this, we don't need to define them in gfx
but can just use the enum directly. (No functional change, just code simplification.)

Differential Revision: https://phabricator.services.mozilla.com/D154238

Bug 650372 - Accept keywords in addition to strings in the @font-face format() hint function. r=emilio

The CSS Fonts 4 spec requires this, and Safari (at least) has long supported it.

Differential Revision: https://phabricator.services.mozilla.com/D154237

Bug 1784058 - Fix up legacy @font-face tests that depended on previous behavior, no longer allowed by the spec. r=emilio

Depends on D154238

Differential Revision: https://phabricator.services.mozilla.com/D154277

Bug 1784058 - Simplify @font-face format hint handling in gfx/thebes, now that it is explicitly only a single hint, not a set. r=gfx-reviewers,aosmond,lsalzman

No functional change, just simplifying the code a bit.

Differential Revision: https://phabricator.services.mozilla.com/D154236

Bug 1784058 - Do not allow a list of strings in the @font-face src descriptor's format() function, only a single format string. r=emilio

This aligns with CSS Fonts 4 (rather than Fonts 3) and with behavior in other browsers;
I don't expect any significant breakage, given that specifying multiple format strings
was never supported in other engines AFAIK, and never served any useful purpose.

Differential Revision: https://phabricator.services.mozilla.com/D154235

I notice there's a lack of test coverage here, so before making changes I'd like to
add a simple set of tests so that we can see the effect of the upcoming fix.

Differential Revision: https://phabricator.services.mozilla.com/D154234

Bug 1783858 - [devtools] Directly pass text and mode when creating a new CodeMirror document in the debugger. r=ochameau.

We used to create the document, then set the text and the mode, which seemed to
trigger unecessary updates in CodeMirror.
Since CodeMirror document can take an initial value and mode, we make this a possibility
in the source editor, and use it from the debugger codebase.

We take this as an opportunity to move the `getMode` function to `source-document.js` as
it's only used from there, and put the logic to not highlight big files there.
The unit test for the function are moved to the same folder the function now lives in,
and are adapted to the new signature.

Differential Revision: https://phabricator.services.mozilla.com/D154096

There is a lot going on in renderer.rs, the initialization code takes a non-negligible chunk of it and touches all aspects of WebRender including setting up all of the threads. This patch moves it into its own init module.
In addition, RendererOptions is renamed into WebRenderOptions to better reflect that it configures every aspect of the engine, and init::create_webrender_instance replaces Renderer::new.

This a rebased version of an pld patch approved by kvark a while back.

Differential Revision: https://phabricator.services.mozilla.com/D103767

Differential Revision: https://phabricator.services.mozilla.com/D153570

Backed out changeset 396e822a4c5d (bug 1623038) for causing mochitest failure in test_fetch_cors.html CLOSED TREE

Differential Revision: https://phabricator.services.mozilla.com/D153606

Differential Revision: https://phabricator.services.mozilla.com/D154373

This issue ports the changes from review D68003 and fixes various build errors occurred in the original review.

Differential Revision: https://phabricator.services.mozilla.com/D154249

Differential Revision: https://phabricator.services.mozilla.com/D154074

Depends on D154213

Differential Revision: https://phabricator.services.mozilla.com/D154214

The next part will try to optimise `indexOf()` when it can be folded to
`startsWith()`.

Differential Revision: https://phabricator.services.mozilla.com/D154213

This is similar to the optimisation for `String.prototype.startsWith`.

Depends on D154211

Differential Revision: https://phabricator.services.mozilla.com/D154212

For now simply call into the VM. Part 3 will add an optimisation when the
search string is a constant.

Depends on D154210

Differential Revision: https://phabricator.services.mozilla.com/D154211

Adding a comma after `JS_FS_END` ensures clang-format will add each entry on a
separate line.

Differential Revision: https://phabricator.services.mozilla.com/D154210

Differential Revision: https://phabricator.services.mozilla.com/D154218

Differential Revision: https://phabricator.services.mozilla.com/D154087