This commit vendors the latest changes to the Suggest and Remote
Settings Rust components.
1. From the `application-services` source tree, I ran
`./tools/update-moz-central-vendoring.py ../m-c` to update the
revisions in the m-c source tree.
2. I added the Remote Settings component UDL file to
`toolkit/components/uniffi-bindgen-gecko-js/mach_commands.py`, and
updated `toolkit/components/uniffi-bindgen-gecko-js/config.toml` to
call the `RemoteSettings` constructor on the main thread. The
Suggest component uses the `RemoteSettingsConfig` type in its
public API, so we must generate bindings for the Remote Settings
component.
3. From the m-c source tree, I ran `./mach uniffi generate` to update
the generated UniFFI bindings.
Differential Revision: https://phabricator.services.mozilla.com/D187559
Support the Pipewire videotransform meta via the already existing shared
infrastructure. This is needed for mobile devices which often have a 90
degree rotated camera - which is likely the reason there is already
support in the shared code paths.
Upstream commit: dc4c019c62abefc09e4903abea44bc36f3427452
Differential Revision: https://phabricator.services.mozilla.com/D183652
This cherry-picks the `spa_meta_videotransform` needed for upcoming
webrtc patches, avoiding a full sync for easier porting.
Upstream commit: 01b2552b71e7475b4c9f893c43e07e8f1044a50b
Differential Revision: https://phabricator.services.mozilla.com/D183651
This can be helpful in various situations, such as debugging with an
unrestricted Pipewire socket or for downstream projects like
B2G/Capyloon. Additionally it will help once we move from the camera
portal to the more generic device portal.
This is intended to get upstreamed but would be nice to carry downstream
already.
Original patch by Fabrice Desré <fabrice@desre.org>
Upstream commit: a717c7ada811411e31bd7308168b4dbee5b956fa
Differential Revision: https://phabricator.services.mozilla.com/D183650
This is part 1 of 3 and vendors the [suggest component](https://github.com/mozilla/application-services/tree/main/components/suggest) from
application-services into m-c. `suggest` depends on `remote_settings`, so it was
also vendored. Part 2 will generate JS bindings with uniffi.
This is my first time doing this so I'll explain how I generated this patch in
case I did something wrong:
1. I manually added `suggest` to the following files:
* Top-level `Cargo.toml`
* `toolkit/library/rust/shared/Cargo.toml`
* `toolkit/library/rust/shared/lib.rs` -- I followed the example of `tabs`,
not sure if `suggest::uniffi_reexport_scaffolding!()` is necessary
2. I ran `./mach vendor rust`
That's it, there were no errors or problems.
Differential Revision: https://phabricator.services.mozilla.com/D187323
The changes from 1830945 were landed upstream in v116's release branch as
commit 04ee24493d as a cherry-pick of dcf600d7a5. dcf600d7a5's no-op file
will be created automatically when running build_no_op_commits.sh at the
proper time so a tracking file for it is not needed yet.
Differential Revision: https://phabricator.services.mozilla.com/D187489
This avoids numerical stability problems when computing the
miter pointer intersection when the lines are nearly parallel.
Differential Revision: https://phabricator.services.mozilla.com/D187057
This updates aa-stroke to c7bc7190f6d3115bc81640c0433649c1fce9491c
which fixes some degenerate behaviour when mitering parallel lines.
Differential Revision: https://phabricator.services.mozilla.com/D186859
This updates aa-stroke to fef8702c4c8afd7d47e7a5aafb6fa347c96b50be
which fixes some degenerate behaviour when mitering parallel lines.
Differential Revision: https://phabricator.services.mozilla.com/D186859
After landing Bug 1826428 to remove jvm_android.cc from the build and
giving time for that to simmer for a while with no known effects, we
can remove our modifications.
Differential Revision: https://phabricator.services.mozilla.com/D186855
Upstream commit: https://webrtc.googlesource.com/src/+/8fbabf340da0bd6c9f1450a8c4522c54390598a1
[M115] Revert mid check in SdpOfferAnswerHandler::CreateDataChannel.
This check was added here:
https://webrtc-review.googlesource.com/c/src/+/300544
When createOffer is used before createAnswer, this check would cause
SetupDataChannelTransport_n to not be called for the remote channel.
(cherry picked from commit 299cdc9057fb8925f1692ac8c7573f51b7872df6)
Bug: webrtc:15258
Change-Id: Ifdab35d1b0260ff03fef4beff13acf8090d59d8f
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/310460
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org>
Cr-Original-Commit-Position: refs/heads/main@{#40357}
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/313620
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Cr-Commit-Position: refs/branch-heads/5790@{#8}
Cr-Branched-From: 2eacbbc03a4a41ea658661225eb1c8fc07884c33-refs/heads/main@{#40122}
We already cherry-picked this when we vendored 151be743d4.
Upstream commit: https://webrtc.googlesource.com/src/+/2abe6e2214fa4fcecdb9614715c55a82c0067e25
[M115] Bail out early if the RTP send module for a SSRC was not found
since it might have been deregistered previously.
BUG=chromium:1454860,chromium:1459124
(cherry picked from commit c0ed83eac258032a2416b7e4200bd074a6455f4b)
Change-Id: I70ba43265361d040e568f83b6400ff8f3c2a8e98
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/311800
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Commit-Queue: Philipp Hancke <phancke@microsoft.com>
Cr-Original-Commit-Position: refs/heads/main@{#40431}
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/312121
Cr-Commit-Position: refs/branch-heads/5790@{#7}
Cr-Branched-From: 2eacbbc03a4a41ea658661225eb1c8fc07884c33-refs/heads/main@{#40122}
