merge_pr_50232

Rename mojo_from_floor to mojo_from_stage

In preparation for actually sending up mojo_from_floor data, this
renames mojo_from_floor in VRStageParameters to mojo_from_stage to
reflect what it actually is.

Bug: 390216623
Change-Id: I3428517b34e614c1c35e206bfafe98893f042fa7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6183158
Commit-Queue: Alexander Cooper [email protected]
Reviewed-by: Elly FJ [email protected]
Reviewed-by: Fred Shih [email protected]
Reviewed-by: Piotr Bialecki [email protected]
Cr-Commit-Position: refs/heads/main@{#1410694}

merge_pr_50258

Convert 2d.composite WPT tests using images to promise tests

This simplifies the offscreen and worker tests a lot, but it also
allows them to be implemented with the same structure as all other
tests, with three distinct sections:

• Draw background.
• Draw foreground.
• Assert

This will help in the follow-up CLs, where these tests will be
migrated to the new test generator. Having the same structure will
allow all of these tests to have a shared base implementation.

The changes in gentestutils.py are pretty hacky, but it's hard to do
anything better given the state of this file. Since this script will be
deleted soon, there's no point in spending time to implement this in
a better way.

Bug: 40207206
Change-Id: I85eab5c12f328bda699d92ab8aecb804100e9d94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6192518
Reviewed-by: Andres Ricardo Perez [email protected]
Commit-Queue: Jean-Philippe Gravel [email protected]
Cr-Commit-Position: refs/heads/main@{#1410563}

merge_pr_50253

[rust png] Legacy codec: Report failure for truncated, complete input.

This CL modifies blink::PNGImageDecoder to call SetFailed when
working with a truncated, complete input. Before this CL the code
has incorrectly treated this situation as recoverable.

After this CL, the behavior of blink::PNGImageDecoder matches that
of blink::SkiaImageDecoderBase. Aligning the behavior it the main
motivation for this CL.

Bug: chromium:391701378
Change-Id: I499a69da6994659ea03dc93967779f691436d0d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6191776
Reviewed-by: Peter Kasting [email protected]
Reviewed-by: Dale Curtis [email protected]
Commit-Queue: Łukasz Anforowicz [email protected]
Cr-Commit-Position: refs/heads/main@{#1410559}

merge_pr_50248

blink: Update MediaKeySession W3C test

This CL updates the W3C test expectations so that onevent handlers are
now compared to both objects and functions. This is because onevent
handlers, when unset, is null, so should be of type object, and when
set, it is of type function.

When using EME Logger, the extension sets it, which causes failures.

Bug: 348059278
Change-Id: I15d980d4a54b98346c89ba06b8d8172ca9e89b8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6020800
Auto-Submit: Vikram Pasupathy [email protected]
Commit-Queue: Vikram Pasupathy [email protected]
Reviewed-by: John Rummell [email protected]
Cr-Commit-Position: refs/heads/main@{#1410582}

merge_pr_50246

Adjust sticky constraint rects to exclude scroll origin

We were previously computing this rect in the space of the scroller, not its physical content space (excluding user scroll offset). For scrollers that have a non-zero scroll origin, the sticky offset resulting was incorrect.

Bug: 40653832

Test: external/wpt/css/css-position/sticky/position-sticky-rtl.html

Change-Id: Ic15d210e0460a07206ebfe8c79bfc6105588db19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6173917
Commit-Queue: Chris Harrelson [email protected]
Reviewed-by: Robert Flack [email protected]
Cr-Commit-Position: refs/heads/main@{#1410413}

merge_pr_50243

Adjust H264 profile-level-id test to avoid false failures.

In preparation of fixing the bug that this test gives coverage for, it
needs to be updated in order to avoid it failing even when things are
working as expected.

If the codec is TRULY recvonly, then it is correct to only negotiate
VP8 and the assertion that H264 needs to be negotiated is wrong.

What we need is a profile-level-id that is "recvonly enough" to only be
listed in RTCRtpReceiver.getCapabilities() but for which we are actually
capable of sending, i.e. there exists some other profile-level-id in
RTCRtpSender.getCapabilities() that is not "==" equal but that is
equal if you "ignoreLevels = true".

64001f is one such profile that is commonly available (level 3.1). On
MacBook M1 Pro where we can send 5.2, this test is applicable.

This test will pass once this WebRTC CL lands:
https://webrtc-review.googlesource.com/c/src/+/374043

Bug: chromium:381407888
Change-Id: I4010d76092bf9b51b20f93e756e2dacf3e8665a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6194115
Reviewed-by: Harald Alvestrand [email protected]
Commit-Queue: Henrik Boström [email protected]
Cr-Commit-Position: refs/heads/main@{#1410504}

merge_pr_50241

Re-enable and improve h264-unidirectional-codec.offer.https.html.

Update WPTs to reflect WebRTC roll of [1] and add a new test.

The H265 tests (both offer to send and offer to receive) now pass
(virtual because H265 is behind flag).

The H264 offer to send test no longer throws in setCodecPreferences()
and it successfully negotiates H264, however the test still fails for
reasons unrelated to the WebRTC fix, which is:

• H264 always offers profile-level-id=64001f (3.1) regardless of which
  level we ask it to offer, in my case 640034 (5.2).
  This is https://crbug.com/391750825.

The new test being added tests that even if we setCodecPreferences()
with a recvonly H264 codec on a sendrecv transceiver, we should still
offer H264 (but with a different level-id) because of codec filtering
being based on ignoring levels.

• This reveals a real bug in webrtc::IsSameRtpCodecIgnoringLevel that
  we should fix in a later CL. The problem is that it only ignores
  level for H265. Other codec comparison algorithms in WebRTC exists
  that do ignore levels for all codecs.

[1] https://webrtc-review.googlesource.com/c/src/+/374520

Bug: chromium:381407888
Change-Id: I2586abc01a955168cb9da1a7f0834a3e0aee049c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6190353
Commit-Queue: Henrik Boström [email protected]
Auto-Submit: Henrik Boström [email protected]
Commit-Queue: Harald Alvestrand [email protected]
Reviewed-by: Harald Alvestrand [email protected]
Cr-Commit-Position: refs/heads/main@{#1410251}

merge_pr_50240

[DIP] Add DIP reporter to DedicatedWorker

This CL adds a DocumentIsolationPolicy reporter for DedicatedWorkers,
based on their DocumentIsolationPolicy. It is stored in the
DedicatedWorkerHost, and communicates with a ReportingObserver bound in
the WorkerContext.

This CL also fixes an issue where the COEP reporter of the
DedicatedWorker was not connected to a ReportingObserver.

This CL is part of a chain of CLs implementing DocumentIsolationPolicy

1. Add DocumentIsolationPolicyReporter
2. Implement DocumentIsolationPolicyReporter
3. Pass the reporter to URLloaderFactory
4. Plumb DIP reporter into ServiceWorkers
5. Add a DIP reporter to DedicatedWorker <- you are here
6. Add a DIP reporter to SharedWorker
7. Plumb DIP reporter in CacheStorage

reporting:
Bug: 333029815, 40176729
Change-Id: I1a1e57ff83e8a55c16c1daec73160e0dcc63bbaa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6187106
Commit-Queue: Camille Lamy [email protected]
Reviewed-by: Mike West [email protected]
Reviewed-by: Hiroki Nakagawa [email protected]
Cr-Commit-Position: refs/heads/main@{#1410263}

merge_pr_50239

[carousel] Support user action pseudos after Carousel pseudo elements

This CL allows user action pseudo classes (e.g. :hover) to be used after
Carousel pseudo elements (::scroll-marker and ::scroll-button)
selectors.

Bug: 388545121
Change-Id: I1c944673c9e0f6624a71a77ad657f79e3c140373
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6182565
Commit-Queue: Daniil Sakhapov [email protected]
Reviewed-by: Rune Lillesveen [email protected]
Cr-Commit-Position: refs/heads/main@{#1410241}

merge_pr_50238

Trusted Types: Improve testing of samples in violation reports. (#50238)

• Trusted Types: Improve testing of samples in violation reports.

w3c/trusted-types#576
w3c/trusted-types#494