Releases: web-platform-tests/wpt
merge_pr_49962
Speculative fix for flaky test
The test's history, e.g. on Linux[1], shows a very consistent pattern
of failing the first test case "touchstart event not received" and then
passing on a second attempt. My attempts at a local repo have not been
successful, but since it seems to be an issue with the state of things
at the beginning of the test and it involves input handling, it would
be good to see what effect waitForCompositorCommit has on the failures.
Bug: 385526611
Change-Id: Iebd9db5272a2d56693f94628b5658d3d03ff9543
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6149989
Reviewed-by: Mustaq Ahmed mustaq@chromium.org
Commit-Queue: David Awogbemila awogbemila@chromium.org
Cr-Commit-Position: refs/heads/main@{#1403186}
merge_pr_49960
Allow setting automatic beacon data from cross-origin subframes.
Cross-origin fenced frames/URN iframes can send automatic reporting
beacons, but currently require data included in these beacons to be
pre-registered via an API call accessible only to a document that is
same-origin to the fenced frame config's mapped URL. This poses a
problem for cross-origin subframes within the same entity (e.g., an ad
frame and a payment subframe from the same company) that need to include
dynamic data, like click information, in the beacon. The current
workaround involves cumbersome postMessage communication and introduces
potential timing issues, highlighting the need for a more practical
solution for cross-origin subframes to set their own beacon data.
This CL relaxes that restriction and lets cross-origin documents set
automatic beacon data as well as use it. This is subject to the same
kinds of opt ins as other cross-origin FFAR features. Namely, the root
frame must opt in via the "Allow-Fenced-Frame-Automatic-Beacons" header,
and the cross-origin subframe setting the data must opt in via the
'crossOriginExposed' parameter in the call to setReportEvent...().
Change-Id: Iea922e737fa870f2edf0c24aa81927535f779d8b
Bug: 382500834
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6074470
Reviewed-by: Andrew Verge averge@chromium.org
Reviewed-by: Dominic Farolino dom@chromium.org
Commit-Queue: Liam Brady lbrady@google.com
Reviewed-by: Arthur Sonzogni arthursonzogni@chromium.org
Cr-Commit-Position: refs/heads/main@{#1403202}
merge_pr_49959
Remove sandersdan from META.yml (#49959)
merge_pr_49958
[Reland, x2] Handle appearance value changes during showPicker. *** GARDENERS: *** Please don't revert this CL again. Simply mark the switch-picker-appearance.tentative.html test as failing in TestExpectations and that should fix the problem. Thanks! When the appearance value changes as the result of the picker opening (e.g. via ::picker(select):open {appearance:auto} or similar), we close the picker to avoid any oscillation or nonsensical behavior. This CL implements this change. The original CL [1] was reverted due to a strange bot failure [2] where the new set of promise_tests somehow fail because blink_wpt_tests is expecting an expectation file with a single blank line. I added a "Failure" expectation to hopefully avoid that, in Patchset 3. The first reland CL [3] was reverted due to a (fairly serious, in my opinion) bug [4] in the WPT importer that was missed by the gardener (it was nuanced) and resulted in this CL getting reverted again. This re-land includes Timeout as a failure mode for all platforms. [1] https://chromium-review.googlesource.com/c/chromium/src/+/6094831 [2] https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/50289/overview [3] https://chromium-review.googlesource.com/c/chromium/src/+/6107689 [4] https://issues.chromium.org/issues/367426156#comment13 Fixed: 376097114,370536090,367426156 Bug: 384394713 Change-Id: I2d22aa452b071ac9eb259dd4ae4e097b970b8851 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6150897 Reviewed-by: Joey Arhar jarhar@chromium.org Auto-Submit: Mason Freed masonf@chromium.org Commit-Queue: Joey Arhar jarhar@chromium.org Cr-Commit-Position: refs/heads/main@{#1403101}
merge_pr_49957
Add WPTs for customizable- buttons appearing after options
See crbug.com/382703187 for details, but a customizable-
customized must come first in the . Placing it after
any content will cause that button to not be the replacement button
for the , but merely a within the options picker.
This set of WPTs simply verifies that this is the case, for several
cases of content-before-.
Bug: 382703187,385675798
Change-Id: I1e5889f5bad956224de878be59c64fa8f58afdcf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6074197
Reviewed-by: Joey Arhar jarhar@chromium.org
Commit-Queue: Joey Arhar jarhar@chromium.org
Auto-Submit: Mason Freed masonf@chromium.org
Commit-Queue: Mason Freed masonf@chromium.org
Cr-Commit-Position: refs/heads/main@{#1403108}
merge_pr_49954
Add support for Ad-Auction-Result-Nonce header for PA B&A
Add support for the alternate authorization flow for Protected
Audiences Bidding and Auction response (as described in
WICG/turtledove#1233).
This feature is behind the FledgeBiddingAndAuctionNonceSupport
feature flag which is going to be enabled by default (for a
waterfall rollout in M133).
Bug: 385128725
Change-Id: Id3c622241c82ed0b71037bfeb1ca5432cd6e66dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6109795
Reviewed-by: Maks Orlovich morlovich@chromium.org
Commit-Queue: Russ Hamilton behamilton@google.com
Reviewed-by: Brendon Tiszka tiszka@chromium.org
Cr-Commit-Position: refs/heads/main@{#1403077}
merge_pr_49953
[Masonry] Introduce parsing for masonry-flow.
This CL introduces the parsing for the CSS property masonry-flow, which
is the shorthand for masonry-direction and masonry-fill.
This is part of: https://chromestatus.com/feature/5149560434589696
The properties are behind the CSSMasonryLayout feature flag. The spec
definition for masonry-flow can be found here:
https://tabatkins.github.io/specs/css-masonry/#masonry-flow.
Bug: 343257585
Change-Id: Icaba5964a6b377a13958e404f7f464e933efc209
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6106736
Commit-Queue: Celeste Pan celestepan@microsoft.com
Reviewed-by: Kurt Catti-Schmidt kschmi@microsoft.com
Reviewed-by: Alison Maher almaher@microsoft.com
Cr-Commit-Position: refs/heads/main@{#1403080}
merge_pr_49952
[text-box-trim] Fix text-box-trim-on-button.html
This CL fixes a typo in the font name of the test.
This patch has no behavior changes.
Fixed: 386860172
Change-Id: I8d324101bb5eb073e82ee5e56e0efae148d40f12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6151520
Auto-Submit: Koji Ishii kojii@chromium.org
Commit-Queue: Lingqi Chi lingqi@chromium.org
Reviewed-by: Lingqi Chi lingqi@chromium.org
Cr-Commit-Position: refs/heads/main@{#1402970}
merge_pr_49951
Revert "Add WPT for Web Speech API events"
This reverts commit 6b9b281088f658531546eddf186fb5076aa442a4.
Reason for revert: Step "chrome_wpt_tests (retry shards) on Windows-11" failing on builder "chromium/ci/win11-arm64-rel-tests"
Example failing build: ci.chromium.org/ui/p/chromium/builders/ci/win11-arm64-rel-tests/3472/overview
Original change's description:
Add WPT for Web Speech API events
This CL adds some basic web platform tests to ensure that the onstart, onend, and onerror events are fired for the Web Speech API.
Change-Id: Ieeaab551b95b56503917e468f9ec33d857790dad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6137598
Commit-Queue: Evan Liu evliu@google.com
Reviewed-by: Yiren Wang yrw@chromium.org
Cr-Commit-Position: refs/heads/main@{#1402727}
Change-Id: I6073a364b704f0aa9df1d7ed38820b3ae5ba4d78
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6147490
Bot-Commit: Rubber Stamper rubber-stamper@appspot.gserviceaccount.com
Commit-Queue: Rubber Stamper rubber-stamper@appspot.gserviceaccount.com
Auto-Submit: Joshua Hood jdh@chromium.org
Cr-Commit-Position: refs/heads/main@{#1402940}
merge_pr_49947
Revert "[Reland] Handle appearance value changes during showPicker." This reverts commit 5fa283f55fea44480ce73308cb12de0274867c1e. Reason for revert: LUCI Bisection has identified this change as the cause of a test failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/test-analysis/b/5657193371140096 Sample build with failed test: https://ci.chromium.org/b/8726470617543936881 Affected test(s): ninja://:blink_wpt_tests/external/wpt/html/semantics/forms/the-select-element/customizable-select/switch-picker-appearance.tentative.html Original change's description: [Reland] Handle appearance value changes during showPicker.
When the appearance value changes as the result of the picker
opening (e.g. via ::picker(select):open {appearance:auto} or
similar), we close the picker to avoid any oscillation or
nonsensical behavior. This CL implements this change.
The original CL [1] was reverted due to a strange bot failure [2]
where the new set of promise_tests somehow fail because
blink_wpt_tests is expecting an expectation file with a single blank
line. I added a "Failure" expectation to hopefully avoid that, in
Patchset 3.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/6094831
[2] https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/50289/overview
Fixed: 376097114,370536090,367426156
Bug: 384394713
Change-Id: I2ab4e43db3de4b7125b564c366fe86bdf9f85cc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6107689
Auto-Submit: Mason Freed masonf@chromium.org
Reviewed-by: Joey Arhar jarhar@chromium.org
Reviewed-by: Mason Freed masonf@chromium.org
Commit-Queue: Mason Freed masonf@chromium.org
Cr-Commit-Position: refs/heads/main@{#1402440}
Bug: 384394713
Change-Id: Ic5392451a1ffe93b40c3a9748164bc03abbfc884
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6148450
Reviewed-by: Bohdan Tyshchenko bohdanty@google.com
Auto-Submit: Danila Kuzmin dkuzmin@google.com
Owners-Override: Danila Kuzmin dkuzmin@google.com
Commit-Queue: Bohdan Tyshchenko bohdanty@google.com
Cr-Commit-Position: refs/heads/main@{#1402871}