Skip to content

Releases: web-platform-tests/wpt

merge_pr_48578

15 Oct 18:54
Compare
Choose a tag to compare

Remove ar_debug requirement for cookie-based debug reporting

WICG/attribution-reporting-api#1441

Bug: 369506940, 330745162
Change-Id: I1dfc23f96e9d7a594c23114ad707ceffcde1161e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5887664
Reviewed-by: Andrew Paseltiner [email protected]
Commit-Queue: Nan Lin [email protected]
Cr-Commit-Position: refs/heads/main@{#1368833}

merge_pr_48494

15 Oct 13:58
9c76757
Compare
Choose a tag to compare

Mark iframe screenshot test as optional (#48494)

merge_pr_48476

15 Oct 20:18
Compare
Choose a tag to compare

Preserve none in computed relative colors without a conversion

Per discussion at w3c/csswg-drafts#10360,
there are a few test cases that incorrectly expect none to be
resolved to 0 in relative colors where no color space conversion was
needed. This CL updates both the test and the behavior in Blink.

Bug: 365818844
Change-Id: I14d6f83d792e4fb4e70171b833de308c66611fb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5905968
Reviewed-by: Fredrik Söderquist [email protected]
Commit-Queue: Kevin Babbitt [email protected]
Cr-Commit-Position: refs/heads/main@{#1368963}

merge_pr_48604

14 Oct 20:53
Compare
Choose a tag to compare

Improve customizable select event handling

This patch restores some of the logic removed in
http://crrev.com/c/5786670 which prevented the popup invoking logic from
running when clicking on descendants of the select element. Without
this, clicking on elements inside the popover would cause the select
popover to close unexpectedly.

Fixed: 369794218
Change-Id: Iad21272eec54fd779a388ff75ab3453a76e34589
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5879126
Commit-Queue: Joey Arhar [email protected]
Reviewed-by: Traian Captan [email protected]
Cr-Commit-Position: refs/heads/main@{#1368409}

merge_pr_48602

14 Oct 17:38
Compare
Choose a tag to compare

WebNN: Implement scatterElements operator in DirectML backend

The scatterElements operator is proposed by WebML WG 1 for
supporting popular transformer-based models.

This CL adds the IDL and mojo definitions of scatterElements, and
implements it in the DirectML backend by mapping to
DML_OPERATOR_SCATTER 2.

This CL also adds the scatterElements validation and conformance tests
into WPT.

Bug: 370536101,370538328
Change-Id: Ifb73bed5eb05cb919b106b4aaea5127ec099edb2
Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5921136
Reviewed-by: Alex Gough [email protected]
Reviewed-by: Weizhong Xia [email protected]
Auto-Submit: ningxin hu [email protected]
Commit-Queue: ningxin hu [email protected]
Commit-Queue: Weizhong Xia [email protected]
Reviewed-by: Rafael Cintron [email protected]
Reviewed-by: Austin Sullivan [email protected]
Cr-Commit-Position: refs/heads/main@{#1368312}

merge_pr_48599

14 Oct 11:33
Compare
Choose a tag to compare

Add WPTs that opus supports both mono and stereo signals.

Currently the first test passes (channelCount:1) but the second test
fails (channelCount:2) because today SDP must be modified to say
"stereo=1".

However the opus spec says that "stereo=1" is just an optional receiver
preference and should not be mandatory to do stereo. Even if it is
missing both mono and stereo should be supported.

The added tests negotiate opus and expect remote track's channel count
to match the local track's channel count in a simple loopback call in
the case that we don't SDP munge.

In a future CL we may want to also test the "stereo=1" SDP munging path
but here we are only concerned with default feature support.

Bug: webrtc:42233792
Change-Id: Ica97b30736d56117b260501e5ccd1c66f2d73fae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5925771
Reviewed-by: Ale Bzk [email protected]
Commit-Queue: Henrik Boström [email protected]
Reviewed-by: Harald Alvestrand [email protected]
Cr-Commit-Position: refs/heads/main@{#1368159}

merge_pr_48598

14 Oct 19:35
Compare
Choose a tag to compare

[@container] Writing-mode change may change container evaluations

For a container-type:size which changes writing-mode, logical size
queries may change evaluation when width != height. Similarly,
scroll-state() queries may change evaluation when mapping of logical
query feature to physical ones change.

Bug: 371829511
Change-Id: I6e4d86c9f0f35ca7f223d4dd73b99ae749f7710b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5915572
Commit-Queue: Rune Lillesveen [email protected]
Reviewed-by: Anders Hartvoll Ruud [email protected]
Cr-Commit-Position: refs/heads/main@{#1368351}

merge_pr_48597

14 Oct 23:29
Compare
Choose a tag to compare

[@container] Correctly match snapped on container-type changes

Unlike for stuck queries, the snapshot client for snapped queries may
outlive a ContainerQueryEvaluator. If a container-type:scroll-state
which is snapped changes its container-type to 'none' and then back
again we may have a snapped state snapshot that does not need an update
when we re-create the ContainerQueryEvaluator.

Make sure the ContainerQueryEvaluator initializes the ContainerValues
with the snapshot state for snapped queries.

Added a test for the stuck feature to verify that works.

Bug: 40279568
Change-Id: I7ced76e4004e9ab7338c6b75b61fe88215438ff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5926649
Reviewed-by: Anders Hartvoll Ruud [email protected]
Commit-Queue: Rune Lillesveen [email protected]
Cr-Commit-Position: refs/heads/main@{#1368471}

merge_pr_48596

14 Oct 12:45
Compare
Choose a tag to compare

[@container] Change serialization of general-enclosed in test

There is an open issue saying this needs to be specified[1].

Change the expectation to align with Gecko and Chromium for now, which
both keep the original serialization for general-enclosed.

[1] w3c/csswg-drafts#7266

Change-Id: I1986ae7a7f63c2c63ef841f047034eeccdc3828d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5925360
Commit-Queue: Rune Lillesveen [email protected]
Reviewed-by: Steinar H Gunderson [email protected]
Cr-Commit-Position: refs/heads/main@{#1368182}

merge_pr_48592

14 Oct 13:16
Compare
Choose a tag to compare

Update Blink to use environment clock timestamps from RTCStats objects.

https://webrtc-review.googlesource.com/c/src/+/363946 added a config flag to tell WebRTC to set environment clock timestamps in RTCStats objects (rather then UTC timestamps). This CL set the config flag, and update the code to handle the new timestamps.

This change make all RTCStats timestamps be expressed as Performance time, fixing chromium:369369568.

Bug: chromium:369369568
Change-Id: Icc991ba55543bf13a17b526a1247043551e85bab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5920098
Commit-Queue: Olov Brändström [email protected]
Reviewed-by: Harald Alvestrand [email protected]
Reviewed-by: Henrik Boström [email protected]
Reviewed-by: Johannes Kron [email protected]
Cr-Commit-Position: refs/heads/main@{#1368191}