Automatic update from web-platform-tests
CCNS BFCache: do not cache CCNS page if WebRTC/Transport/Socket used
In the current implementation, if the WebRTC/WebTransport/Websocket
connections are closed, the non-sticky feature will be removed and the
page will be eligible for BFCache.
However, the page may contain some sensitive data that are retrieved
over these channels before the connection closure, so we should not
store the CCNS page into BFCache.
This CL also create `kAllowedForNonCacheControlNoStoreFeatures` for
those features that are allowed for non-CCNS page BFCache, and moved
`kAuthorizationHeader` over.
Bug: 1446619
Change-Id: Ic2e1e49d50fe522b1a66c6e011cb6fa83670d05d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4549039
Commit-Queue: Mingyu Lei <leimy@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159467}
--
wpt-commits: d8b86fb0f11027ffa73c2251dd1decdbe97144ac
wpt-pr: 40121
Automatic update from web-platform-tests
Prerender: Use |IsDisallowedHttpResponseCode| in
|MakeDidCommitProvisionalLoadParamsForActivation|.
This CL uses |prerender_navigation_utils::IsDisallowedHttpResponseCode|
in |MakeDidCommitProvisionalLoadParamsForActivation| to make the
expectation of allowed http status code consistent.
Bug: 1441842
Change-Id: If690bf5d10936c3fc920c31bdaf27b7cbacad8ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4609824
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Huanpo Lin <robertlin@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159464}
--
wpt-commits: f09a88ae0309aa892fae13dc49ca072a89b247e1
wpt-pr: 40581
Automatic update from web-platform-tests
Apply font-size-adjust to fallback fonts
Fallback fonts ignore font-size-adjust. That is because the primary
font's description is used to create fallback fonts. As a fallback font
can have different font metrics, we should adjust its size.
The subpixel rendering might affect the result on Windows. To make it
happy, we tweak the font size in font-size-adjust-012.html. With this
change, Windows gets a regression on font-size-adjust-010.html due to
unknown reasons. We will handle it in a separate ticket [1].
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1454612
Test: external/wpt/css/css-fonts/font-size-adjust-012.html
external/wpt/css/css-fonts/font-size-adjust-metrics-override.html
Bug: 451346
Change-Id: Iab8f14c21fdf501931e62e77e9059737722a050f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4305200
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Commit-Queue: ChangSeok Oh <changseok.oh@bytedance.com>
Cr-Commit-Position: refs/heads/main@{#1159352}
--
wpt-commits: 921aaae3e84c182fe2d09ef176a3f03702928a8c
wpt-pr: 40210
Automatic update from web-platform-tests
Expect shortest serialization for offset-path / offset-anchor (#40611)
When only one value is specified, the second is always center.
--
wpt-commits: 6f296e42b3bd9dbd89d3472a175e448c97609215
wpt-pr: 40611
Automatic update from web-platform-tests
Allow button to have writing mode vertical
This CL allows <button> and <input> types "button", "submit", "reset",
"file" to have writing-mode vertical for both the default native
appearance and when appearance is set to none.
We also put the change behind the feature flag
FormControlsVerticalWritingModeSupport so it can be turned on safely.
Change-Id: I1f6cc53a1eaef640e3d968d0e7ec5fc248879b50
Bug: 681917
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4617874
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159261}
--
wpt-commits: 289e601bed8bd71bd29ae61c336b1281c35b33b2
wpt-pr: 40577
Automatic update from web-platform-tests
Close other <details> elements linked by name attribute in tree order.
When <details> elements are linked by their common name attribute values
into an exclusive accordion, and one member of the group is closed, this
closes the linked <details> elements in tree order rather than insertion
order. This reverts much of 34b2758acd53c3ab7ff32bf418334792ad13e523.
The code is simpler but slower, and it matches typical web platform
patterns more closely (even if those patterns may not be ideal in this
case).
This change is based on discussion in
https://github.com/whatwg/html/pull/9400/files#r1221692104
This change also stops treating the empty string as a valid name, and
adds a test to match. This matches the above HTML PR.
Bug: 1444057
Change-Id: I5eed9e25ff7698e23738e53445c64c0fc3a1b035
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4617028
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159237}
--
wpt-commits: 606530b23a2ed89e965403475c6f40a98afb0900
wpt-pr: 40563
Automatic update from web-platform-tests
[scroll-start] Apply scroll-start after layout
scroll-start[1] should set the initial/default scroll position of a
scroller. Many different things may cause a scroller's size/layout
to change as a page loads which can affect how scroll-start should
be applied. So, this patch applies scroll-start on each frame until
the scroller has been explicitly scrolled, i.e. by the user or via a
programmatic scroll. After an explicit scroll, scroll-start is no
longer applied.
We propagate scroll-start from the document element to the viewport
so that scroll-start can be applied to the page. We save an
explicitly_scrolled_ bit on the element so that scroll-start
does not prevent saved (explicit) scrolls from surviving changes
to display and overflow.
[1] https://drafts.csswg.org/css-scroll-snap-2/#scroll-start
Bug: 1439807
Change-Id: I5655f8e74b85fe45038f700091065fa11eeac0f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4546420
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159106}
--
wpt-commits: 4203f37b7415c420aa495d315339e8e5b51b8288
wpt-pr: 40083
Automatic update from web-platform-tests
Add the ability to disconnect DOM Parts
This turns out to be important, at least in the case of writing
tests. `disconnect()` is a one-way operation; there's no way to
re-connect a part to its part root.
This CL also adds the constraint that NodePart can't have child parts.
It therefore adds exceptions to the constructors for NodePart and
ChildNodePart in the case that a NodePart is supplied.
Bug: 1453291
Change-Id: Ied398c417b1e105c77a95c3836ee2d09902df7c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4617275
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159094}
--
wpt-commits: 84d8aa38655c6c1a010703fc07479108427b3a04
wpt-pr: 40603
Automatic update from web-platform-tests
Add part caching and ordering to DOM Parts
Previously, parts were added to the list, and returned, in the order
they were constructed for a given root. Now, that list is stored as
an unsorted list, and when `getParts()` is called, a cached, sorted
list is returned.
NOTE: This CL does not add cache invalidation code where needed, so
moving nodes around in the DOM tree will not invalidate the cache.
Cache invalidation will be added and tested in a subsequent CL.
Bug: 1453291
Change-Id: I542b07520002202bfdc31d4341dca6cbffdc8b5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4616676
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1159056}
--
wpt-commits: 0868cb809d40d179379ad406c7da9c07a69429d9
wpt-pr: 40573
Automatic update from web-platform-tests
Revert "View timeline: Handle offscreen stickiness."
This reverts commit 8164954aefce51cc59f95da80c0acce888a1bc0b.
Reason for revert: Causing flaky failures, e.g. https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/20525/overview.
Original change's description:
> View timeline: Handle offscreen stickiness.
>
> A view timeline subject inside a position:sticky box can get "stuck"
> from any of the four CSS offset properties (left, top, right, bottom)
> during any of the named view-timeline ranges (entry, contain, exit) or
> even while it is entirely outside the viewport.
>
> ViewTimeline::CalculateOffsets previously assumed that stickiness occurred only when the subject was fully contained by the viewport.
> This change implements the more general solution.
>
> Bug: 1448294
> Change-Id: I842552b3a30078587eff6287e4ee11396d13ed95
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4616159
> Reviewed-by: Kevin Ellis <kevers@chromium.org>
> Commit-Queue: Steve Kobes <skobes@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1158852}
Bug: 1448294
Change-Id: I6d0bcfae16ee2265a2a1a442a646452ea89341e8
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4621249
Reviewed-by: Steve Kobes <skobes@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158962}
--
wpt-commits: 4bdf59dc15828cdea946ef812a58c1567a10a884
wpt-pr: 40597
Automatic update from web-platform-tests
Add additional end-to-end success Private Aggregation WPTs
Renames some files as a drive-by and fixes .ini files to simply disable
the tests that have exclusive virtual tests instead of having errors
as expected.
Bug: 1452248
Change-Id: I7e30e4ce4bf2fa8d2d3f5fb8e56ea21563851e3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4617351
Reviewed-by: Yao Xiao <yaoxia@chromium.org>
Commit-Queue: Alex Turner <alexmt@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158889}
--
wpt-commits: 05eb26701d4390759662070c397f0232910323b7
wpt-pr: 40592
Automatic update from web-platform-tests
View timeline: Handle offscreen stickiness.
A view timeline subject inside a position:sticky box can get "stuck"
from any of the four CSS offset properties (left, top, right, bottom)
during any of the named view-timeline ranges (entry, contain, exit) or
even while it is entirely outside the viewport.
ViewTimeline::CalculateOffsets previously assumed that stickiness occurred only when the subject was fully contained by the viewport.
This change implements the more general solution.
Bug: 1448294
Change-Id: I842552b3a30078587eff6287e4ee11396d13ed95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4616159
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158852}
--
wpt-commits: dd6156ef5158cc1538250af5ed20f0909c7bdfce
wpt-pr: 40562
Automatic update from web-platform-tests
Add basic end-to-end Private Aggregation Web Platform Tests
These tests ensure that a report makes it to the expected endpoint.
Only tests in Shared Storage worklets for now
Bug: 1452248
Change-Id: I70ad2180c7cde93beb5ffe08fe3c1a091bf298d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4598993
Reviewed-by: Yao Xiao <yaoxia@chromium.org>
Auto-Submit: Alex Turner <alexmt@chromium.org>
Commit-Queue: Alex Turner <alexmt@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158824}
--
wpt-commits: e8b5a2b60fe757f14677bb5e30cac1f48498f16d
wpt-pr: 40502
Automatic update from web-platform-tests
Add mojo js support to wpt runner for AndroidWebView (#40545)
We need this capability in order to use the gen directory for Android WebView.
--
wpt-commits: 3ee01a45b5becc64a3de8ad3faf5b1c1a17175f4
wpt-pr: 40545
Automatic update from web-platform-tests
[wdspec] browsingContext.print: fix rounding error in page.py test (#40504)
* [wdspec] browsingContext.print: fix rounding error in page.py test
[pytest](7a087d54be/webdriver/tests/support/image.py)
uses:
def cm_to_px(cm): return round(cm * 96 / 2.54)
[js](7a087d54be/tools/wptrunner/wptrunner/print_pdf_runner.html)
uses:
const viewport = page.getViewport({ scale: 96. / 72. });
...
canvas.height = viewport.height;
canvas.width = viewport.width;
This produces a rounding error, even though the dimension is correct:
> assert cm_to_px(expected_dimensions["height"]) == height
E assert 454 == 453
E +454
E -453
The inconsistency of rounding in both ends becomes clear when we
eliminate "round" in the pytest side:
> assert cm_to_px(expected_dimensions["height"]) == height
E assert 453.54330708661416 == 453
E +453.54330708661416
E -453
There are multiple ways to fix this issue.
Option #1: Use "floor" instead of "round" in pytest.
Option #2: Use a range in the assertion comparison, allowing a
difference of up to +-1.0. This is what this PR does.
The comparison is performed in
[`assert_pdf_dimensions`](b6107cc1ac/webdriver/tests/support/fixtures_bidi.py (L210)).
The problematic part is .96 / .72 which evaluates to 4/3 = 1.333333....
* use floor in cm_to_px instead of round
* compare to floor and to round instead of a range
* Revert "compare to floor and to round instead of a range"
This reverts commit 63f894e6d1881616e0f13b7a40ddcb30b772eba8.
* Revert "use floor in cm_to_px instead of round"
This reverts commit 7e65d918b25575060ca50009d261d1e76dca6cae.
--
wpt-commits: fb57353809aa19c0659ece5563d05ed20706d1fc
wpt-pr: 40504
Automatic update from web-platform-tests
Add popover top layer content-visibility tests (#40541)
Copy existing top layer tests that are based on dialog and
adapt the tests to use popover instead.
--
wpt-commits: d6c561438a8ba351be0aef3350d57694d4f2c282
wpt-pr: 40541
Automatic update from web-platform-tests
Make ::backdrop stay in top layer while animating out
This patch adds a new internal pseudo class which matches popovers while
they are still in the top layer after they have been closed in order to
also make the corresponding ::backdrop stay in the top layer.
This is based on futhark's patch:
https://chromium-review.googlesource.com/c/chromium/src/+/4554016
HTML spec PR: https://github.com/whatwg/html/pull/9387
Fixed: 1449145
Change-Id: I8e4831e960c5d18fb077f023c119fd0e678541df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4585724
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158640}
--
wpt-commits: 83976e7d1f6a7b175947209736bd40e94a7cae77
wpt-pr: 40369
Automatic update from web-platform-tests
Remove XRSessionDeviceConfig.uses_input_eventing and related code (#40530)
This commit removes the uses_input_eventing_ variable from the
XRSessionDeviceConfig interface and all the code that relied on it.
The XRSessionDeviceConfig.uses_input_eventing feature was originally
added to support WMR but is no longer needed since no runtimes support
it now.
Bug: 1429644
Change-Id: I6d691f67e20d5f430169556b215e038c6b1c3173
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4604546
Quick-Run: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1157619}
Co-authored-by: Mahmoud Ahmed <mahmoudaahmedd@gmail.com>
--
wpt-commits: 866ccc0efe52a1614e020ce45975b7d1e77df282
wpt-pr: 40530
Automatic update from web-platform-tests
Fix test 2d.text.draw.baseline.ideographic.html
The ideographic baseline is defined as follows:
https://drafts.csswg.org/css-writing-modes-4/#line-under: the
line-relative “bottom” or descender side. (The side underlines are
typically drawn on.)
I attached result here:
https://bugs.chromium.org/p/chromium/issues/detail?id=1066953#c14
(It's with font 50 and draw at height 50)
I think this test case is wrong: The test case draws text at ideographic
under baseline at height 31.25, so that text is draw above 31.25 and
leaves 31.25 to 50 to be at its original color (red for test). The test
tests if the resulting rect, rect(0, 0, 50, 100), to be all green.
I think the test needs to know the location of the green rectangle and
move it down. The test is updated.
Bug: 1066953
Change-Id: I2b9c029a439fd8a19343dc826b70b1bc1c95b60e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4615191
Commit-Queue: Yi Xu <yiyix@google.com>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158349}
--
wpt-commits: 6f807d8f42ea14bdb03d943f4adf2f950f15909d
wpt-pr: 40554
Automatic update from web-platform-tests
Add a Part collection to PartRoot and connect it up
This CL just adds a `parts_` collection to `PartRoot`, and updates
it in the naive way any time a new Part is constructed. No Node
tracking is done or anything, so it's completely possible that if
a Node is moved to another document, the parts list will be out of
date.
Bug: 1453291
Change-Id: I1fa01e0543dfe52974ac6175728f5fe79c7c3b93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4609624
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158287}
--
wpt-commits: 435846e6d26a61feec408588685ca77c5d535024
wpt-pr: 40571
Automatic update from web-platform-tests
[FedCM] Actually run the multi-IDP tests
Due to an incorrect merge conflict resolution in
https://chromium-review.googlesource.com/c/chromium/src/+/3924487/56..58
these tests never actually ran.
The problem is that they are skipped in the base test suite (as
expected), but the virtual test suite inherits the Skip expectation
and the line that changes it to Pass has been removed by accident.
Bug: 1348262
Change-Id: I2711c3607f727fa5f92e32833c7b645e31ba2f66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4617005
Reviewed-by: Zachary Tan <tanzachary@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158248}
--
wpt-commits: 293bb6c2a9dfb3c1f4c0507f0fdbfc79c2917bb2
wpt-pr: 40570
Automatic update from web-platform-tests
WebSocket: add wpt for sending 50 65K messages
http://crrev/c/3311025 introduced a bug when sending messages a multiple
of 65536 bytes in size over a connection with backpressure. This was
fixed in http://crrev/c/3404081 in January 2022, however no repro test
was added at that time.
Add a wpt to repro the issue and stop it happening again.
BUG=1454078
Change-Id: Icdc1dab66e58bab6eaabec84c0f53d5f17ca28e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4612732
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158168}
--
wpt-commits: 4b1b05d5bd421c7fcf3005307ece3b0e651f59f6
wpt-pr: 40542
Automatic update from web-platform-tests
Further DOM Parts hierarchy reorg, and connect Document to Parts
In implementing the connection between DocumentPart and Document,
it became apparent that there were other issues with the previous
hierarchy. Notably, Document owned DocumentPart, which was a Part,
which therefore had a |root| reference back to DocumentPart. That
made it impossible to require Part to always have a |root|.
This CL revamps the hierarchy once more, to this:
PartRoot (getParts, clone)
/ \
DocumentPartRoot Part (root, metadata)
/ \
NodePart (node) ChildNodePart (prev/next/etc)
With that, a Part always has a reference to its |root|, and the
DocumentPartRoot can be owned by Document and always non-nullptr.
This CL also connects DocumentFragment to DocumentPartRoot.
Bug: 1453291
Change-Id: Ic0f34d3572321cf12fb960d75243e05462c9fe84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4604678
Commit-Queue: David Baron <dbaron@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158222}
--
wpt-commits: 248252e558f4030ccb34a396b7cfb0c24a8d71d4
wpt-pr: 40523
Automatic update from web-platform-tests
Raise DOM exceptions if layer API is incorrectly used.
It's invalid to call `endLayer()` without a matching `beginLayer()`.
Likewise, calling `restore()` after `beginLayer()` isn't allowed.
Calling `save()` without a matching `restore()` outside of layers
however is allows to preserve existing functionality. We want to be
stricter with usage of the new layer API, at least at first, because
as soon as we start allowing degenerate API uses, Hyrum's law will
make sure we'll have to support these forever.
Bug: 1396372
Fixed: 1237275, 1403977
Change-Id: I76e83217fafe60248f8e4ae81ceafb1215dda9bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4572867
Commit-Queue: Jean-Philippe Gravel <jpgravel@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1158153}
--
wpt-commits: a44ca1286f13670ca201d5a10588848e6fcb6a61
wpt-pr: 40292
Automatic update from web-platform-tests
[A11y] Reland targeted cached property invalidation
Relands the following CLS:
* Enhance performance by targeting value updates to specific nodes, commit 704633e6846e44b20c488a3eb98fa43c2c8e4591.
* Don't queue anything for irrelevant attribute changes, commit 2c66a62ed62e601b7a81271e4be4f9e173ce9afc.
* Add comment explaining call to UpdateStyleAndLayoutTreeForNode(), commit 73b9eed3b48bc8ce70de657672755f44a89e7358.
* Ensure cached values not invalidated during the computation of them, commit 4d167a62cd13d5209ecefb664e3690ac955bc559.
* Run a test with --force-renderer-accessibility that used to fail, commit cab7ecd829b24acf677e02f8f118085eaad7f799.
* Simplify code to update cached focusable state, commit 79cb184e5dab5f6084ec78d485bd9496eaa0aaf8.
* Simplify code that invalidates cached values on an AXObject, commit 6df79a50a55fe5cf99d2c50f7308e1236361b771.
Fixed: 1446864, 1446550, 1434555, 1362758
Change-Id: I16855bdcb746cb41387b69e1e97ab72ffc47e342
Cq-Do-Not-Cancel-Tryjobs: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4545510
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Jacques Newman <janewman@microsoft.com>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1157878}
--
wpt-commits: 777cb340853c108820173827aaef668eb06c8e9a
wpt-pr: 40488
moz-wptsync-bot
Mingyu Lei
Robert Lin
ChangSeok Oh
Luke Warlow
David Choi
Tim Nguyen
Di Zhang
L. David Baron
David Awogbemila
Mason Freed
Evan Stade
Reilly Grant
Dan Clark
Alex Turner
Steve Kobes
Ben Wiser
Thiago Perrotta
Daniil Sakhapov
jgraham
Vitor Roriz
Rob Buis
Joey Arhar
Blink WPT Bot
Yi Xu
Christian Biesinger
Adam Rice
Jean-Philippe Gravel
Takashi Sakamoto
Chris Dumez
Aaron Leventhal