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

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

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

Bug 1812615 - Update to Glean v52.2.0, glean_parser 7.0.0 and UniFFI 0.23. r=chutten,markh,glandium,supply-chain-reviewers

The in-tree UniFFI bindings were regenerated with:

    ./mach uniffi generate

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

Bug 1788119 - Part 4 - Update mp4parse-rust for AVIS support. r=kinetik,glandium,supply-chain-reviewers

Depends on D156652

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

Backed out 5 changesets (bug 1788119) for causing bustages complaining about AVIFDecodedData. CLOSED TREE

Backed out changeset 430e71478ff5 (bug 1788119)
Backed out changeset 9493029c76b9 (bug 1788119)
Backed out changeset 7d5cc211e3f5 (bug 1788119)
Backed out changeset 3eaac75dde3c (bug 1788119)
Backed out changeset 1f8eacf96c71 (bug 1788119)

Bug 1788119 - Part 4 - Update mp4parse-rust for AVIS support. r=kinetik,glandium,supply-chain-reviewers

Depends on D156652

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

Backed out changeset 56abc66f7e84 (bug 1788119)
Backed out changeset 00d82acfaa2f (bug 1788119)
Backed out changeset 4ba88410cdf6 (bug 1788119)
Backed out changeset eeb1461933aa (bug 1788119)
Backed out changeset 8dce9350abb8 (bug 1788119)

Bug 1788119 - Part 4 - Update mp4parse-rust for AVIS support. r=kinetik,glandium,supply-chain-reviewers

Depends on D156652

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

Colors can now be defined in different color spaces with the color()
function.

https://w3c.github.io/csswg-drafts/css-color-4/#predefined

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

This updates the version wpf-gpu-raster which adds support for
GPUs/drivers that use truncation instead of rounding when converting
vertices to fixed point.

It also adds the GL vendor to InitContextResult so that we can detect
AMD on macOS and tell wpf-gpu-raster that truncation is going to happen.

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

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

Bug 1811284 - Update wgpu to 24a904256e225b20b11fb30f914ef53212a2909e. r=webgpu-reviewers,ErichDonGubler,jimb

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

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

This matches the empty-and-published-to-crates.io crate, which should allow for
easier optional dependencies in Rust.

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

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

Bug 1352757 - Add lab(), lch(), oklab(), oklch() to specified colors. r=supply-chain-reviewers,emilio

Use new changes from cssparser and use the new lab/lch/oklab/oklch color
formats.

Introduced a new color type AbsoluteColor.  It represents any kind of
color that has absolute numerical values.  It is also tied to a color
space and therefore can be trivially converted to another color space.

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

Backed out changeset 218b12b92ccb (bug 1352757) for causing failures on test_transitions_per_property.html.

Bug 1352757 - Add lab(), lch(), oklab(), oklch() to specified colors. r=supply-chain-reviewers,emilio

Use new changes from cssparser and use the new lab/lch/oklab/oklch color
formats.

Introduced a new color type AbsoluteColor.  It represents any kind of
color that has absolute numerical values.  It is also tied to a color
space and therefore can be trivially converted to another color space.

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

Backed out changeset 8e353f0600a8 (bug 1810495)
Backed out changeset d75d527cdeee (bug 1810495)

Depends on D166915

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

Picks up a single fix to address a deadlock triggered when attempting to
configure an audio device that has been removed.

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

Bug 1793784 - Replace the minidump_writer_linux crate with the minidump-writer crate r=glandium,supply-chain-reviewers

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

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

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

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

Started callback interface functionality to UniFFI.  Currently this only
supports the async fire-and-forget use case, where Rust queues a JS
function to run, but doesn't wait (or `await`) for the response.

The basic system is:

  - The JS code registers a callback interface handler with the C++
    code.  This handler is responsible for the specifics of invoking the
    callback.
  - The C++ code defines a function to call a JS handler.  Once the JS
    handler registers itself with C++, the C++ registers it's function
    with Rust.
  - The C++ code queues the call to the JS main thread.
  - Because of how UniFFI handles callback interfaces, the C++ code can
    be "dumb".  UniFFI sends a object id, method id, and RustBuffer
    encoding all arguments.  This means C++ doesn't need to care about
    the specific arguments, they get unpacked by JS.

I tried to keep the generated code as simple as possible by moving the
complexity to static code.  For JS this meant writing a generic
`UniFFICallbackHandler` class in the static code that the generated code
constructs.  For C++ this meant the generated code defines a
`UniFFIGetCallbackInterfaceInfo` function that returns a struct with all
the data specific to a callback interface (it's name, the UniFFI
scaffolding init function, etc).  The static code can then define a
generic `QueueCallback` function that looks up the callback interface
info using the interface ID and then makes the call.

Allow UniFFI functions to run on the main thread rather than always
being dispatched to a worker thread.  This allows us to test invoking
callback interfaces from the main thread thread. I don't think we will
use this much currently, since we don't want to block the main thread
for any significant amount of time. However, this will pair well with
the next step in the project which is async -- allowing async Rust
functions to call async JS functions. In that scenario, dispatching to
the worker thread is unnecessary.

Callback interface objects present a potential memory leak, since you
can easily create a cycle between a JS Callback object and a UniFFIed
Rust object, and the GC has no way of detecting it.  To try to detect
these there's some shutdown code that checks that there are no callbacks
registered during shutdown and prevents any future callbacks from being
registered.

Added a `config.toml` file and code to parse it.  This is needed to
specify which functions should run on the main thread.

Updated the git commits for the several UniFFI examples/fixtures.

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

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

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

The postprocessing phase that cleaned up `pytoml`'s output has little
effect on `toml`'s output, which is already largely clean. Remove the
additional code.

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

Remove explicit sorting, as this is no longer needed to guarantee
determinism as of Python 3.6 (our minimum-supported version).

(This is a separate commit solely to make it clear that the reordering
of `.cargo/config.in` is indeed merely a reordering and contains no
hidden functional changes.)

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

This brings in various bugfixes and improvements from upstream,
including the fix for bug 1791809 and a workaround for bug 1804530.

In this update, `wgpu_core` leaves the selection of backends to its
users, rather than trying to guess which backends to use itself, based
on the target architecture and operating system. For Firefox, this
means that `gfx/wgpu_bindings/Cargo.toml` is now responsible for
selecting back ends.

Firefox's WebGPU implementation should never use `wgpu`'s GLES
backend. Firefox can now explain this to `wgpu-core`, causing it to
drop its dependency on `glow`, `bitflags_serde_shim` and `slotmap`.
These are no longer vendored, and their exemptions in
`supply-chain/config.toml` can be dropped.

The new `wgpu-core` updates to version 0.37.1+1.3.235 of the `ash`
crate, and this patch moves ash's supply-chain exemption forward to
the new version. We expect to finish vetting that next week, but
because this `wgpu-core` update is urgently needed, we want to extend
the exemption for the time being.

The dependency on `slotmap` had been patched to an empty file in
`build/rust/dummy-web`, which can now be removed.

The new `wgpu-core` no longer uses `cfg_aliases`, so Firefox no longer
needs to vendor that.

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

Depends on D164781

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

Backed out changeset e6becf16d643 (bug 1788306) for causing bustage on UniFFICallbacks.cpp. CLOSED TREE

Started callback interface functionality to UniFFI.  Currently this only
supports the async fire-and-forget use case, where Rust queues a JS
function to run, but doesn't wait (or `await`) for the response.

The basic system is:

  - The JS code registers a callback interface handler with the C++
    code.  This handler is responsible for the specifics of invoking the
    callback.
  - The C++ code defines a function to call a JS handler.  Once the JS
    handler registers itself with C++, the C++ registers it's function
    with Rust.
  - The C++ code queues the call to the JS main thread.
  - Because of how UniFFI handles callback interfaces, the C++ code can
    be "dumb".  UniFFI sends a object id, method id, and RustBuffer
    encoding all arguments.  This means C++ doesn't need to care about
    the specific arguments, they get unpacked by JS.

I tried to keep the generated code as simple as possible by moving the
complexity to static code.  For JS this meant writing a generic
`UniFFICallbackHandler` class in the static code that the generated code
constructs.  For C++ this meant the generated code defines a
`UniFFIGetCallbackInterfaceInfo` function that returns a struct with all
the data specific to a callback interface (it's name, the UniFFI
scaffolding init function, etc).  The static code can then define a
generic `QueueCallback` function that looks up the callback interface
info using the interface ID and then makes the call.

Allow UniFFI functions to run on the main thread rather than always
being dispatched to a worker thread.  This allows us to test invoking
callback interfaces from the main thread thread. I don't think we will
use this much currently, since we don't want to block the main thread
for any significant amount of time. However, this will pair well with
the next step in the project which is async -- allowing async Rust
functions to call async JS functions. In that scenario, dispatching to
the worker thread is unnecessary.

Callback interface objects present a potential memory leak, since you
can easily create a cycle between a JS Callback object and a UniFFIed
Rust object, and the GC has no way of detecting it.  To try to detect
these there's some shutdown code that checks that there are no callbacks
registered during shutdown and prevents any future callbacks from being
registered.

Added a `config.toml` file and code to parse it.  This is needed to
specify which functions should run on the main thread.

Updated the git commits for the several UniFFI examples/fixtures.

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

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

We also artificially update nix to 0.25 in preparation for bug 1793784.

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

Bug 1804545 - Re-vendor application-services to pickup fix to IDs in sync payload. r=skhamis,supply-chain-reviewers

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

This adds machinery to wpf-gpu-raster and aa-stroke to support an output buffer specified as
a slice, which they will preferentially use instead of their dynamic Vec to store output
vertexes in.

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