Automatic update from web-platform-tests
[text-box-trim] Support vertical flow
In doing this, this patch adds the `FontBaseline` variations
of `Alphabetic()`, `CapHeight()`, and `XHeight()` in the
`FontMetrics` class.
Also, the rounding methods in `AdjustEdges()` were different
from what `FontMetrics::FixedAscent()` does. This patch adds
`Fixed` variants to `FontMetrics` to make reviewing the
consistency easier.
All changes are under a currently disabled runtime flag.
Bug: 40254880
Change-Id: I470f1df976ff210ee7c3cdb336b73f44a59909d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5539097
Reviewed-by: Kent Tamura <[email protected]>
Auto-Submit: Koji Ishii <[email protected]>
Commit-Queue: Koji Ishii <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301750}
--
wpt-commits: 044beefe2fe9706c899bd503c5953abf07546fc0
wpt-pr: 46283
Automatic update from web-platform-tests
Remove dependency on experimental document policies in tests
There are several internal and external tests which rely on experimental
document policy features to demonstrate the operation of document policy
itself. This CL updates these tests to use more well-standardized
features instead.
Bug: 340920459
Change-Id: I8bccbb6f86ffae4dfcd086bf2947a0adac5eb107
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5539454
Reviewed-by: Chris Harrelson <[email protected]>
Commit-Queue: Ian Clelland <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301744}
--
wpt-commits: 147cb9c4b0752992efb463a0eea72f64f688f840
wpt-pr: 46291
Automatic update from web-platform-tests
Fix external/wpt/service-workers/cache-storage/cache-abort.https.any.js
stash-put takes two parameters. Added "value=close" as suggested.
Below are the errors we see from the bots:
File "/b/s/w/ir/third_party/blink/web_tests/external/wpt/fetch/api/resources/stash-put.py", line 37, in main
value = request.GET.first(b'value')
File "/b/s/w/ir/third_party/wpt_tools/wpt/tools/wptserve/wptserve/request.py", line 576, in first
raise KeyError(key)
KeyError: b'value'
Bug: 340680128
Change-Id: I0a6037b3bfa58ed12a64269aff390cd8a21ba3a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5540916
Reviewed-by: Joshua Bell <[email protected]>
Commit-Queue: Weizhong Xia <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301655}
--
wpt-commits: 32eb4ec77a89c784eec207a91f0cf74028f6f47e
wpt-pr: 46272
Automatic update from web-platform-tests
Let document.caretPositionFromPoint work correctly in text control.
If the point is inside input/text area element, the `CaretPosition`
should have `offsetNode` pointing to the text control element instead
of the inner editor element inside the user-agent shadow tree.
The behavior is also defined in step 4 of the
spec[1].
[1]: https://drafts.csswg.org/cssom-view/#dom-document-caretpositionfrompoint
Bug: 41487363
Change-Id: I1c024bdf6ce9620905a28487c8c91383f2086a54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5531199
Reviewed-by: Koji Ishii <[email protected]>
Reviewed-by: Sanket Joshi <[email protected]>
Reviewed-by: Mason Freed <[email protected]>
Commit-Queue: Siye Liu <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301622}
--
wpt-commits: dd39fe69148b964aa2db4ce7003eeabad1ac7caa
wpt-pr: 46211
Automatic update from web-platform-tests
Set minimum target size of 24px for appearance:base-select
According to accessibility guidelines, we must ensure that all of the
pointer targets in appearance:base-select must be at least 24x24 CSS
pixels. https://github.com/openui/open-ui/issues/1026
Bug: 1511354
Change-Id: Iba814399e4061f7ce36c24296aef37a540444612
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503502
Commit-Queue: Joey Arhar <[email protected]>
Reviewed-by: David Baron <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301595}
--
wpt-commits: f23e47a0774b10c5af7de68d5d89fdd07b41871d
wpt-pr: 45998
Automatic update from web-platform-tests
Rename position-anchor:implicit to position-anchor:auto
This was resolved here:
https://github.com/w3c/csswg-drafts/issues/10312#issuecomment-2112984254
and will be added to the spec shortly.
This is observable, but barely. After this CL, `implicit` won't be a
valid value for `position-anchor`, so it'll resolve to the default
value of `auto`. Meaning the behavior will be the same. But via the
CSSOM, getComputedStyle(element).positionAnchor will now return "auto"
instead of "implicit".
Fixed: 340206288
Change-Id: I75b05310638dca70aa6aa8807da8cfe7c9624a32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5540275
Reviewed-by: Rune Lillesveen <[email protected]>
Commit-Queue: Mason Freed <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301585}
--
wpt-commits: 6bdb665f70cda739fe30fad86cc89fef3b81e535
wpt-pr: 46269
Automatic update from web-platform-tests
[RWI] Require user activation for real world identity API
BUG=338261531
Change-Id: If5967b8db446f717129384c53e0b741920d72b4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5532484
Commit-Queue: Peter Kotwicz <[email protected]>
Reviewed-by: Christian Biesinger <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301496}
--
wpt-commits: 53eba699dbe6d5366af14d726f42814fd86fc310
wpt-pr: 46216
Automatic update from web-platform-tests
[soft navigations] Refactor navigation heuristics
This CL refactors the navigation heuristics and related API, simplifying
the requirements and data flow.
URL change detection
-------------------------
Previously, soft nav heuristics tracked both a "has-url-change" bit and
a string URL, initially empty. Both needed to be set to be considered a
soft nav, which is redundant. This CL removes the "has-url-change" bit,
set in SameDocumentNavigationStarted(), relying solely on the string URL
set in SameDocumentNavigationCommitted().
Additionally, the relevant SoftNavigationContext is passed to
SameDocumentNavigationCommitted() to simplify the data flow. For metrics
purposes, calling SameDocumentNavigationCommitted() with a null context
records SoftNavigationOutcome::kNoAncestorTask (previously this was
recording in SameDocumentNavigationStarted()).
Context propagation
-------------------------
For async same-document navigations, i.e. renderer -> browser ->
renderer, the navigation task state must be propagated to the commit so
it can be restored for the events (popstate). This works the same as before, except:
- SameDocumentNavigationStarted() is renamed to
AsyncSameDocumentNavigationStarted(), and it's only called for async
navigations.
- AsyncSameDocumentNavigationStarted() handles registering the current
task with the task attribution tracker.
- A bug was fixed where the propagated context could be lost in the
navigation API plumbing, which was necessary for consistency of the
popstate event as well as being able to pass the relevant context to
SameDocumentNavigationCommitted().
Tests
-------------------------
- A unit test is added to ensure we don't accidentally emit the same
soft nav more than once. A previous version of this CL was doing
that, and it was only accidentally caught by a bug in another test
(below).
- This fixes a web components soft-nav WPT test. The pushState in the
connected callback was not having an effect since the test already
called pushState. This was found during testing.
Bug: 40942324
Change-Id: Ic7723251e8f7b277d0572f29ae0c2ea8d400c1bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5458385
Reviewed-by: Yoav Weiss (@Shopify) <[email protected]>
Commit-Queue: Scott Haseley <[email protected]>
Reviewed-by: Ian Clelland <[email protected]>
Reviewed-by: Michal Mocny <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301456}
--
wpt-commits: bc6f2e351c9f95de457fc4654d9cdb74327ffb9c
wpt-pr: 45811
Automatic update from web-platform-tests
Make worker rAF test non-tentative (#46284)
--
wpt-commits: 4c4bfc3253ad37d124458e21e5dbaad2514be9d5
wpt-pr: 46284
Automatic update from web-platform-tests
WebNN: Allow 0-D (scalar) reductions
crrev.com/c/5448942 added a restriction on the reduction ops
(including argMin/argMax) that the rank of the input tensor must be
greater than zero.
In https://github.com/webmachinelearning/webnn/issues/681, @fdwr
points out that 0-D (scalar) reductions are fine, it's just a no-op.
Per that discussion, this removes a restriction. There are already
WPT cases for argMin/argMax (although they fail for other reasons);
cases are added for the plethora of reduction ops (which also fail
for other reasons).
Change-Id: Ib10a9b0bb3062f9d2b6001d9a4963b14e751d14f
Cq-Include-Trybots: luci.chromium.try:mac14-blink-rel,mac14.arm64-blink-rel,win11-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5529350
Reviewed-by: Phillis Tang <[email protected]>
Reviewed-by: ningxin hu <[email protected]>
Commit-Queue: Joshua Bell <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301369}
--
wpt-commits: 22a06eb294cd23846add1c8ca8e234bc9d7260c6
wpt-pr: 46209
Automatic update from web-platform-tests
Check thread id is in current frames (#46266)
On Chromium Windows bot, we are seeing KeyError below. Check the thread
id is in sys._current_frames() before format_stack, otherwise do not
include the stack in the error message.
Error message:
00:02:16.943 WARNING: Exception in TestExecutor.run:
File "C:\b\s\w\ir\third_party\wpt_tools\wpt\tools\wptrunner\wptrunner\executors\base.py", line 219, in run
message += "".join(traceback.format_stack(sys._current_frames()[executor.ident]))
KeyError: 8372
--
wpt-commits: c55cca3cabaa78d029191694e7efaff229f9c0a7
wpt-pr: 46266
Automatic update from web-platform-tests
Add WPT for PA navigation + window.fence.notifyEvent
Opening a new top-level page in a PA fenced frame requires user
activation, and notifyEvent does as well. This test ensures that
whichever of these occurs first consumes transient activation,
preventing the other.
Change-Id: I8d39797bd0abdf49e5c4c05e182c0132e67c8754
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5522343
Commit-Queue: Andrew Verge <[email protected]>
Reviewed-by: Liam Brady <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301317}
--
wpt-commits: 6929570884cb167927c8b0044c0feb7354944bb8
wpt-pr: 46144
Automatic update from web-platform-tests
Make transform property parse not trip up at !important.
After recent parser changes, every property needs to be able to
break cleanly on an unexpected token, such as !important. Transform
was inadvertently missed (except for the case of “none”), so fix that.
Fixed: 340100643
Change-Id: I45521e331090c5d554218726a9b260b584014940
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5538019
Reviewed-by: Anders Hartvoll Ruud <[email protected]>
Commit-Queue: Steinar H Gunderson <[email protected]>
Auto-Submit: Steinar H Gunderson <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301278}
--
wpt-commits: 0d3d3166f3b34717a829056dc35304725a58da79
wpt-pr: 46280
Automatic update from web-platform-tests
Implement the ic-height metric of font-size-adjust
This change introduces support for the ic-height metric in
font-size-adjust [1], allowing developers to adjust font size based on
the height of the CJK water glyph. Notably, in cases where the chosen
font lacks the CJK water glyph or vertical font information, we apply no
adjustment. If the standard says something different later, we will
follow it up [2].
[1] https://www.w3.org/TR/css-fonts-5/#valdef-font-size-adjust-ic-height
[2] https://github.com/w3c/csswg-drafts/issues/6384
Test:
animations/responsive/interpolation/font-size-adjust-responsive.html
external/wpt/css/css-fonts/animations/font-size-adjust-composition.html
external/wpt/css/css-fonts/font-size-adjust-ic-height.tentative.html (new)
external/wpt/css/css-fonts/parsing/font-size-adjust-computed.html
external/wpt/css/css-fonts/parsing/font-size-adjust-valid.html
Bug: 1219875
Change-Id: Ie90a6241cb7e8a55fcaf65df5a4edc1058028ebe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5118658
Commit-Queue: ChangSeok Oh <[email protected]>
Reviewed-by: Dominik Röttsches <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301206}
--
wpt-commits: 0e158ca24ba911457f330c61b01722bafc82c7bc
wpt-pr: 43637
Automatic update from web-platform-tests
Add a workflow to publish the container image to ghcr.io (#42423)
This PR adds a job that would allow GitHub users with [the write access](https://docs.github.com/en/packages/learn-github-packages/publishing-a-package) to publish a Docker image to the GitHub registry. The current version requires manually defining the GitHub image tag but it could be further automated in the future.
The goal of this CL is to test publishing before testing if task cluster can use the published image.
More details about publishing packages https://docs.github.com/en/packages/learn-github-packages/publishing-a-package
Issue #28903
--
wpt-commits: 48e6484fee5fecb92ed969f46f2839b85164c4b1
wpt-pr: 42423
Automatic update from web-platform-tests
[text-box-trim] Fix when there is an initial-letter
`text-box-trim` is supposed to trim all parts above the point
specified by the `text-box-edge`. This patch fixes initial
letter boxes preventing the trimming, similar to
crrev.com/c/5539108 fixed for the Ruby annotation.
This patch has no behavior changes as the changes are under a
runtime flag.
Bug: 40254880
Change-Id: I7741f6a78e34371959d4ab3ca9cb8a5a9a2a8460
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5540990
Auto-Submit: Koji Ishii <[email protected]>
Commit-Queue: Lingqi Chi <[email protected]>
Reviewed-by: Lingqi Chi <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301161}
--
wpt-commits: d11ce9e05714b062ad3b9cb4184e65763cdc2393
wpt-pr: 46277
Automatic update from web-platform-tests
[text-box-trim] Fix when there is a Ruby annotation
`text-box-trim` is supposed to trim all parts above the point
specified by the `text-box-edge`. This patch fixes Ruby
annotation preventing the trimming.
This patch has no behavior changes as the changes are under a
runtime flag.
Bug: 40254880
Change-Id: I52f40bbba919beddad398c4400b5715b6e5f2fb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5539108
Reviewed-by: Kent Tamura <[email protected]>
Commit-Queue: Kent Tamura <[email protected]>
Auto-Submit: Koji Ishii <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301089}
--
wpt-commits: ed61cad1fd266b46dc25edd9656ba636b660e9cf
wpt-pr: 46276
Automatic update from web-platform-tests
[text-box-trim] Add a test for floats and BFC
This patch adds a test for how a box with `text-box-trim`
resolves the BFC offset.
This patch has no behavior changes.
Bug: 40254880
Change-Id: I92f5b86d3ce07f612c52c7a76e5faa94010f5ed4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5537810
Reviewed-by: Lingqi Chi <[email protected]>
Commit-Queue: Koji Ishii <[email protected]>
Reviewed-by: Kent Tamura <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301081}
--
wpt-commits: b5cfef8d1c4e75ccb4669b1cb38a3fe56a3ed942
wpt-pr: 46258
Automatic update from web-platform-tests
CSS highlight pseudos: resolve styles for ::search-text
This patch resolves the styles for ::search-text twice during element
style recalc (once for :current, once for :not(:current)), and once
for :not(:current) only during getComputedStyle [1].
We use StyleRequest::SearchTextRequest to tell the resolver which
state we want styles for, which then gets plumbed to the selector
checker via ElementRuleCollector, ContextWithStyleScopeFrame, and
SelectorCheckingContext.
SelectorChecker then uses that request to decide whether a selector
with :current is a match, but only when the last dynamic pseudo was
::search-text (using a SelectorCheckingContext flag, like we do for
::selection:window-inactive).
[1] <https://github.com/w3c/csswg-drafts/issues/10297>
Bug: 339298411
Change-Id: Id8cb1cc14399318a18d305f54b64b686a5c6d60a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5528894
Reviewed-by: Anders Hartvoll Ruud <[email protected]>
Commit-Queue: Delan Azabani <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1301073}
--
wpt-commits: 3a7dc02c636e569c65292e4152e183aeaf7c2722
wpt-pr: 46197
Automatic update from web-platform-tests
Rename WebNN test with space in the filename (#46254)
The old filename wasn't recognized as a test at all.
--
wpt-commits: e0791095c7abd9b884868040643507df9f6ea822
wpt-pr: 46254
Automatic update from web-platform-tests
Remove outdated mention of Travis CI (#46250)
Just call it CI, like in the "Running Tests on CI" docs.
--
wpt-commits: 1789aef322ff2d9e891d519979bcffa5997dff96
wpt-pr: 46250
Automatic update from web-platform-tests
Don't require EME closed promises to resolve in any specific order (#46268)
The promise from .close and from .closed() should be equivalent in all cases. So long as both promises resolve in the correct order relative to everything else, that should be sufficient.
--
wpt-commits: 915d40b37fbd3554548d5cbec9f335f329ccc944
wpt-pr: 46268
Automatic update from web-platform-tests
Add WPT coverage of Sec-CH-Width
This patch adds WPT coverage of Sec-CH-Width:
https://wicg.github.io/responsive-image-client-hints/#sec-ch-width
This re-lands https://crrev.com/1300292 with the following changes:
1. The test now ensures the image onload handler does not fire before
the test runs using an onload attribute.
2. The test now uses a sizes attribute, which is required per spec.
3. The test now works on platforms with different device pixel ratios.
Bug: 335630145
Change-Id: I77d64d4394d5ced924ed1e92ba2110b5237114f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5537569
Auto-Submit: Philip Rogers <[email protected]>
Reviewed-by: Traian Captan <[email protected]>
Commit-Queue: Traian Captan <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1300949}
--
wpt-commits: b70defdd6adc5eb0d836e28c1adec76e2097c9e6
wpt-pr: 46248
Automatic update from web-platform-tests
[WPT] fix feature/privacy-policy-frame-policy-timing
Seems like these have been disabled a lot of places, let's improve the
test to resolve the issues. Given the issues are intermittent and
timeout related, let's tighten up the order of operations and see if
that helps.
Bug: 340363659
Change-Id: I46a63043effa73e0c7bf5ac489e6d83159b4f4c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5537049
Auto-Submit: Ari Chivukula <[email protected]>
Reviewed-by: Ian Clelland <[email protected]>
Commit-Queue: Ian Clelland <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1300841}
--
wpt-commits: 6818346ef85cfdd0dfa39a846df32496e3556951
wpt-pr: 46261
Automatic update from web-platform-tests
Implement getSelectionRects feature for TextMetrics
This change creates a new API method for TextMetrics objects in canvas
that uses font data and precalculated text runs, to calculate the
selection rects for an interval of characters. This interval is defined
by character positions in the input text.
The selection rects are calculated using the existing
`Font::SelectionRectForText` method, but on a logical run by run
basis to ensure correct management of bidi text inputs.
The target is to match the rects that would be obtained by using the DOM
from selecting this same interval using
`Selection.getRangeAt(0).getClientRects()` after having set the selection
with a range.
The new API was enabled under the `ExtendedTextMetrics` flag.
Change-Id: Ia05ce8e55e3e73a491354293502b457ad712026e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5353031
Reviewed-by: Jean-Philippe Gravel <[email protected]>
Reviewed-by: Fernando Serboncini <[email protected]>
Commit-Queue: Andres Ricardo Perez <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1300725}
--
wpt-commits: 12f8a9095c895763d4165d93c80f04ae9bcd32a7
wpt-pr: 46057
Automatic update from web-platform-tests
Get border/padding from fragment when painting background.
Since @page border box layout objects aren't in the the layout tree, any
code that wants to walk up the tree to find the containing block will be
in for a surprise.
This would happen if percentage-based @page padding was used [1].
Recomputing padding during painting when we have already done it during
layout is rather pointless anyway. Read it out directly from the
fragment.
[1] #1 blink::LayoutBox::ContainingBlockLogicalWidthForContent()
#2 blink::LayoutBoxModelObject::ComputedCSSPadding()
#3 blink::LayoutBoxModelObject::PaddingTop()
#4 blink::LayoutBoxModelObject::PaddingOutsets()
#5 blink::BoxPainterBase::PaintFillLayer()
#6 blink::BoxPainterBase::PaintFillLayers()
#7 blink::BoxFragmentPainter::PaintBackground()
Bug: 40286153
Change-Id: I1e6e92c2ce1d81aab2673ec9a877eac455534102
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5526469
Commit-Queue: Morten Stenshorne <[email protected]>
Reviewed-by: Xianzhu Wang <[email protected]>
Reviewed-by: Ian Kilpatrick <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1300711}
--
wpt-commits: 601b701a9d708b48a9cddae1ac15963d61be7964
wpt-pr: 46252
Automatic update from web-platform-tests
Update scroll to text fragment test mapping (#46249)
The feature was renamed in web-features:
https://github.com/web-platform-dx/web-features/pull/1007
Additionally include some tests of the interaction with other features.
This results in some tests being tagged with multiple features, which
could potentially be used to filter out tests depending on the
implementation status of the different features.
--
wpt-commits: dab963f555e6136cf4a51e4f162937996f3ce732
wpt-pr: 46249
Automatic update from web-platform-tests
Reland "[text-box-trim] Fix `text-box-edge` to be inherited"
This is a reland of commit 66b9710a5337aaefeb1a4e71ba5675b2a8744cb2
The original CL caused performance regressions at
crbug.com/339684347. This is likely because, as a result of
the change, a same explicit `field_group` had both inherited
and non-inherited as in comment 13 of the issue.
This patch changes the `field_group` to `*`, and add it to
`css_properties_ranking.json5`. As the feature hasn't shipped
yet, the ranking order is just a guesstimate.
Original change's description:
> [text-box-trim] Fix `text-box-edge` to be inherited
>
> As per the spec for:
> * `text-box-trim`: https://drafts.csswg.org/css-inline-3/#propdef-text-box-trim
> * `text-box-edge`: https://drafts.csswg.org/css-inline-3/#propdef-text-box-edge
>
> Bug: 41494590
> Change-Id: I934e272f964fce6f2c57818c94102046fc0f309a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5532122
> Commit-Queue: Koji Ishii <[email protected]>
> Commit-Queue: Kent Tamura <[email protected]>
> Auto-Submit: Koji Ishii <[email protected]>
> Reviewed-by: Kent Tamura <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1299895}
Bug: 41494590
Change-Id: Ia16086866b7b67f187495a3d1968b210abb2e956
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5531316
Reviewed-by: Kent Tamura <[email protected]>
Commit-Queue: Koji Ishii <[email protected]>
Reviewed-by: Lingqi Chi <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1300538}
--
wpt-commits: 00c155959f0a01db082b1cce4de8b1fbbcc63563
wpt-pr: 46245