Automatic update from web-platform-tests
Conditionally use initiator for about:blank navigations
The HTML Standard demands that for new browsing context group creation,
the initiator document's full URL (uncensored by referrer policy) be
used as the new document's `document.referrer`.
https://crrev.com/c/3763042 first implemented this change, however it
made the assumption that whenever the initiator frame token is set, the
initiator frame is present and can be referenced. Due to form submission
scheduling, the initiator document might no longer exist by the time we
try and synchronously navigate the new document to `about:blank` (via
the form submission), and as a result we were null-dereferencing the
initiator that is already done.
This CL fixes the bug by only referencing the initiator document during
new document creation *if* the new document exists (not just if the
initiator frame token was set). This technically violates the spec, but
the test I add in this CL ensures that:
1. The crash is fixed
2. The correct spec expectations are in place, despite us failing
I'm considering changing the spec in this instance anyways, since it
might not make sense for the spec strongly reference the initiator if
it might not exist otherwise, but that is a separate issue.
R=rakina@chromium.org
Bug: 1370425
Change-Id: Ib34bee1211afec90e57a7cd804fc80f84a04e0fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963738
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1061005}
--
wpt-commits: 0b90ee44c7d6924e0328abead70fd17ee4b3015a
wpt-pr: 36546
Automatic update from web-platform-tests
Add test for backpressure on MediaStreamTrackProcessor (#36522)
* Add test for backpressure on MediaStreamTrackProcessor
--
wpt-commits: 1774ecf6c03b184d583fbacb1d3f05f946452762
wpt-pr: 36522
Automatic update from web-platform-tests
[@container] style() and pseudo elements
We used the wrong element as the first possible style container for
pseudo elements (skipped the originating element).
Bug: 1375308
Change-Id: Ia54cf0994f8ec1c0dcce073710526cc409a15e4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963057
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060921}
--
wpt-commits: 18e9c305744ffb7656a12ba8850b6e705b26c1ee
wpt-pr: 36525
Automatic update from web-platform-tests
Fix a read-buffer-overflow when CSS Nesting is active.
The test case uses a data: URL to construct a stylesheet
that does not end in a newline, which is required for this
bug to manifest. In debug mode, it hits a DCHECK.
Fixed: 1376067
Change-Id: I2106ddee503d46c9d86917aadc4ce6938f4a9b56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3964569
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060907}
--
wpt-commits: dad7be7ab78613088e175884a8d6850464dfca3f
wpt-pr: 36536
Automatic update from web-platform-tests
XHR FormData: add tests for changes to the entry list during iteration
This is similar to #36455 and #20445: we want to make sure that adding and deleting elements during iteration is reflected in FormData's value pairs to iterate over (i.e., iteration does not happen on a cached version).
--
wpt-commits: bfa61347807bc133f4a8afeb9f0ccc47abf1f0bd
wpt-pr: 36532
Automatic update from web-platform-tests
Enforce referrer policy restriction for prerendering
A previous CL implemented the list of sufficiently strict speculative
navigation referrer policies, but only applied it to prefetch. We now
apply it to all speculation rule actions.
We also fix some existing prerender referrer policy tests.
referrer-policy-mismatch.html incorrectly hyphenated the policy.
referrer-policy-origin.html used the origin policy which is not one of
the sufficiently-strict referrer policies. We switch to using the
strict version.
Bug: 1176054, 1355146
Change-Id: I5b3c89d92ce80dc6b37ddb429786cf1d6d4a806b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3957475
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060751}
--
wpt-commits: bc528db416c80cf4723a58db3ad03e7282136ac3
wpt-pr: 36496
Automatic update from web-platform-tests
[FedCM] Test headers sent during manifest request in WPT
This CL:
- Makes WPT tests test headers sent during manifest request
- Renames manifest from fedcm.json to manifest.py
- Moves fedcm related support files to support/fedcm
- Refactors fedcm-network-requests.sub.https.html to modify default
test options in order to make tests more robust.
BUG=368434
Change-Id: I75ee3a027e700bef47f2a42f17b61b3a970308ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3961388
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060741}
--
wpt-commits: c733de556e408c21c529142992dd912f64e15071
wpt-pr: 36497
Automatic update from web-platform-tests
Reland "Don't take snapshot in CSSScroll/ViewTimeline constructor"
This reverts commit 523abfdbf0b4ca8c3ed7ece06781eedb6c154587.
Reason for revert: Test failures fixed
Note to sheriffs: Please do not revert this patch if it breaks builds,
as it involves a lot of tests. Just file a bug and assign to
xiaochengh@.
Original change's description:
> Revert "Don't take snapshot in CSSScroll/ViewTimeline constructor"
>
> This reverts commit a0391c51ec5cbea5aab72e0d732a3098996897b6.
>
> Reason for revert: Causing build failures crbug.com/1374585
>
> Original change's description:
> > Don't take snapshot in CSSScroll/ViewTimeline constructor
> >
> > CSSScrolltimeline and CSSViewTime objects are created as part of style
> > recalc. However, they currently takes scroll offset snapshot when
> > constructed, which is not spec-compliant (spec says taking snapshot once
> > per frame update before style recalc) and violates pipeline stages.
> >
> > Hence, this patch removes snapshot taking from the constructors.
> >
> > The behavior change is that if a scroll timeline is created due to a
> > style change, it won't be activated in an immediate getComputedStyle()
> > call, but need to wait until the next frame update. This aligns with
> > scroll offset changes. As a result:
> > - Many web tests add waitForNextFrame() before getComputedStyle()
> > - A unit test is changed into web test, because snapshotting is not
> > part of LocalFrameView::UpdateLifecyclePhases(), but current part of
> > update animation steps.
> >
> > Bug: 1371217
> > Change-Id: Idb0397f241ae579b580c71b01889e92fb7471bde
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3935343
> > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> > Reviewed-by: Kevin Ellis <kevers@chromium.org>
> > Cr-Commit-Position: refs/heads/main@{#1058924}
>
> Bug: 1371217,1374585
> Change-Id: I067597633a3e03eace5522454c20fe6cc5149693
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3956549
> Reviewed-by: Peter Williamson <petewil@chromium.org>
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Owners-Override: Peter Williamson <petewil@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1059546}
Bug: 1371217
Cq-Include-Trybots: luci.chromium.try:linux_chromium_dbg_ng
Change-Id: I44e0b1d388a5e428220d4f6edf1947c478fda419
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3964106
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060716}
--
wpt-commits: 056571bfa3a3e71058676d2a39c8917ed0f840fa
wpt-pr: 36537
Automatic update from web-platform-tests
May need relayout when fragmented OOF moves.
First of all, LayoutBox::CachedLayoutResult() performs some debug
cloning if the object NeedsLayoutOverflowRecalc(), and then does
CheckSameForSimplifiedLayout(), which would fail if we're fragmented.
Just avoid that DCHECK in this case. It's true that actual simplified
layout doesn't allow fragmented content, but we're not actually
performing simplified layout in this case.
When NGBlockNode::Layout() decides to replace the layout result, even if
we did hit the cache, though, we'll now make sure that we don't hit the
cache again when resuming layout. This is just so that we end up in
NGFragmentItems::FinalizeAfterLayout() when done with the last fragment.
I couldn't think of a better way, although it doesn't seem strictly
necessary to miss the cache.
Bug: 1374625
Change-Id: I4601c2f14886730907e961a1e38dfc31ada4c49f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3959886
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060694}
--
wpt-commits: ad947b6d1f3976f9a54e15200e4c5c9a462ecd36
wpt-pr: 36521
Automatic update from web-platform-tests
WPT for changing parent baseURI doesn't affect srcdoc child baseURI.
Adds a web platform test to verify that changing the baseURI of a
srcdoc iframe's parent doesn't affect the baseURI of the srcdoc frame
itself. Tests both regular and sandboxed srcdoc iframes.
Bug: 1356658
Change-Id: I0f80e13320ada90b14826a775a92b08b236c4864
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3932751
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: James Maclean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060679}
--
wpt-commits: 87b4d09f4d2f3cee1703056a36f7419d835781f1
wpt-pr: 36239
Automatic update from web-platform-tests
Fix transform-translate-background-{001,002}.html ref (#36476)
The spec says transforms should only be ignored for the background-image, so the scrollbar change caused by the transform should still be reflected. Use a negative margin-top to do that.
Fixes#36454
--
wpt-commits: b1719ff4762d131b81a1b1dbb7c1d43d68c7c849
wpt-pr: 36476
Automatic update from web-platform-tests
Snap Border, Outline, and Column-Rule Widths before Layout
Chrome renders a 1 pixel gap
between a parent's border and a child's background,
when a sub pixel borders widths decimal value is
greater than or equal to 0.5.
This happens because
* the parent's size gets calculated at layout time with
the sub pixel values
* the child's position gets calculated based on the
parent's position and size
* the border width gets floored at paint time to just the whole value
This leaves a 1 pixel gap between
the last pixel in the parent's border and
the first pixel in the child's background.
This behavior is a regression introduced in:
https://chromium-review.googlesource.com/c/chromium/src/+/2199140
This CL is also reverting the subpixel border width behavior of
https://codereview.chromium.org/2640143005
Which changed Chrome to
"Use floor instead of round for decimal border widths"
with the intent to increase interop with Firefox and Safari
which both floor borders.
Previously Chrome was rounding the borders at Paint time,
avoiding the gaps between a parent's border and a child's background.
The proposed fix is to snap (floor) the borders widths before
layout, matching what Gecko and WebKit do.
Outline widths also use `ConvertBorderWidth` as their conversion
function and will also be snapped before layout.
While Column-Rule widths were already snapped before layout by
`StyleBuilderConverter::ConvertLineWidth`,
with this CL they will also use
`StyleBuilderConverter::ConvertBorderWidth`
in order to unify the snapping of widths behavior and code paths.
CSS isses:
https://github.com/w3c/csswg-drafts/issues/5210https://github.com/w3c/csswg-drafts/issues/7473
R=pdr
Change-Id: Ib32ba28e4f193ba79f90f96771378abaf0c589a8
Bug: 1120347, 1201762
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3717365
Reviewed-by: David Baron <dbaron@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Traian Captan <tcaptan@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Owners-Override: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060652}
--
wpt-commits: 250c39d10718c061fa6640eeb6d64b66e0968681
wpt-pr: 36189
Automatic update from web-platform-tests
Storage buckets: don't recreate non-default bucket in Cache Storage
Appropriately handle the case where a bucket is deleted and the
CacheImpl is still alive. Also handle the case where we are
calculating usage for non-default buckets.
Bug: 1372140
Change-Id: Ia66afe099bf9f996175c27583666629f15d8cf6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3950713
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Andrew Williams <awillia@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060641}
--
wpt-commits: 879c8b0c98d15028cb38907c327169d5652f70e0
wpt-pr: 36442
Automatic update from web-platform-tests
[FedCM] Improve CSP Test
This CL improves the FedCM CSP test so that the test fails if the
FedCM API does not respect CSP.
Change-Id: Ibfebea806b34aa0c1b5e0f4fbf503e395f0a1d94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3961791
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060625}
--
wpt-commits: 560ae9d738dccb7b82045c01c845cc850559e1fe
wpt-pr: 36513
Automatic update from web-platform-tests
Pre-walk tree during adoption to WillMoveToNewDocument()
Before adopting a tree into a new TreeScope, pre-walk the tree being
moved and notify all the nodes that they will be leaving the current
document, if applicable. This allows them to do clean-up work, such
as unregistering event handlers.
Bug: 1343016
Change-Id: I2c43a87cdac3fd1398145aa24f7da27b24d15d00
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3919946
Auto-Submit: Frank Liberato <liberato@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060615}
--
wpt-commits: 73403629844705303666a6df49fef2fd258cd5cd
wpt-pr: 36267
Automatic update from web-platform-tests
The height of <select> with attribute size (#36478)
* Don't let the calculation difference of <select> with attribute size affects this test
--
wpt-commits: 46bd66b0995763ca0dcb8bf11566733328d9e72a
wpt-pr: 36478
Automatic update from web-platform-tests
OOFs in column spanner with column balancing
If an OOF was contained by a column spanner, and then we were to do a
column balancing pass after it had been aggregated to the multicol
builder, we would end up clearing out the OOFs inside the builder
within the column balancing pass. Then we would never lay out the OOF
inside the spanner.
To fix this, skip clearing out the OOFs in the builder when column
balancing.
Bug: 1358030
Change-Id: If5603b6ab71f24e9ff07aabeb5bc20ccdbe260d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3961636
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060493}
--
wpt-commits: 8c5b0fe827665b208a2cc787836ba9e43e37b1d3
wpt-pr: 36511
Automatic update from web-platform-tests
Fix#36326: stop daily runs of Servo
These have been broken since January, and there's been few people
noticing or having the interest to fix them, so let's just stop using
Taskcluster capacity to run it except when explicitly triggered.
Co-authored-by: jgraham <james@hoppipolla.co.uk>
--
wpt-commits: a633361f5848e53a24068bcb85defa6986a5ff92
wpt-pr: 36437
Automatic update from web-platform-tests
Parse 'crossorigin' value earlier in HTMLTrackElement::LoadTimerFired
The HTMLMediaElement from which the attribute is read could potentially
disappear when we (synchronously) dispatch the 'error' event during the
DidCompleteLoad(kFailure) call. Perform the parsing of the attribute
string directly to avoid keeping a reference to the attribute value.
Bug: 1374341
Change-Id: I207c45377204c674eff68ee42e630004358f903f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3955996
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Auto-Submit: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/main@{#1060431}
--
wpt-commits: 9f4fa391f4434ee8bf11f49b75f3d5a1cc54ce5c
wpt-pr: 36459
Automatic update from web-platform-tests
Frameset NG: Fix a regression with orthogonal writing-modes
NGConstraintSpaceBuilder::SetAvailableSize is logical for the
container, not for the child.
Bug: 1375947
Change-Id: I5b1d9492177fdc8df8f2e236dc8767eb74beead6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3962573
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060369}
--
wpt-commits: 5e3581b12d704afcee812d98014cf2b88f788cfe
wpt-pr: 36516
Automatic update from web-platform-tests
Fix HTML map element not matching image using id attribute
The specs specify that, regardless of HTML versus XML syntax, matching
the map element with an img using `usemap` attribute should be done
using either the `name` or the `id` attributes, rather than using the id
attribute only for the XML syntax [1].
This also fixes the code that considers both id and name (which was
previously done only for XML syntax) to consider both of them when both
are present, rather than only the one specified later.
[1] https://html.spec.whatwg.org/multipage/#image-map-processing-model
Change-Id: Iea193333637a324543323b7e432352ce2c438295
Fixed: 108489
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3953777
Commit-Queue: Di Zhang <dizhangg@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1059535}
--
wpt-commits: 0e5ceaff59c0ff3121df5b6cd8fffc882afff011
wpt-pr: 36461
Automatic update from web-platform-tests
Add meta timeout=long to charset-parameter test
It gets the occasional timeout failure, so this will give it more
time to run.
Fixed: 1374068
Change-Id: Id8291eb4f8797ecb84071e32657b075048c690bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3961551
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060232}
--
wpt-commits: 60c12a6237bc397c2cd6f2c850f7d3340bb8d50f
wpt-pr: 36510
Automatic update from web-platform-tests
Regenerate 2d.filter.canvasFilterObject.componentTransfer.identity.tentative.html
This should make the "update-built" CI check pass again.
PR #36401 ("Batch-remove unused arguments in _assertPixel and _assertPixelApprox") seems to have accidentally removed an extra empty line that's added by the test generation scripts.
--
wpt-commits: 1d89ad9625baf040d26ca51dfe4e08e5bf7ffe7f
wpt-pr: 36519
Automatic update from web-platform-tests
[WPT] Avoid getComputedStyle().length in failure output
Every time we add or remove a property, we have to rebaseline these.
But the exact number of properties is actually not very interesting
information, so just avoid it in the output altogether.
Change-Id: I22a608b378fb7a0b65a19fb760fa24df71cb6237
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3962828
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060365}
--
wpt-commits: ddc605698746c41f4b9c0dd4ffc5a4dbc4f0275b
wpt-pr: 36517
Automatic update from web-platform-tests
Append trailer data to serialized messages.
This reserves space in the Blink envelope for an offset to trailer
data appended to the message which stores summary information about
the message without needing to deserialize it.
This allows quickly assessing which WebIDL interfaces must be exposed
for the message to be deserialized successfully, which means a
messageerror event can be dispatched instead of a message event, even
without eagerly deserializing (as the spec suggests).
This is a major change that requires a bump to the serialization format
and would require care to revert in the future.
Bug: 1341844,1366065
Change-Id: I45904ff3f6270ac0e31c49dfae45c72c7e0d135b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3758405
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1060228}
--
wpt-commits: a658bffda5e18c74d88ab4727cb713ce8223880c
wpt-pr: 35526
Automatic update from web-platform-tests
[wptrunner] Enable print-reftests for content shell (#36471)
This is done by passing the 'print specifier over stdin.
Tested with:
xvfb-run wpt run ... infrastructure/reftest/*-print.html \
--metadata=infrastructure/metadata
All except `reftest_mismatch_page_margins-print.html` should pass
(`@page` does not currently work).
--
wpt-commits: 3e008889ffe512f5148b78f3cfe86b5522666a67
wpt-pr: 36471
Automatic update from web-platform-tests
Let the table layout algo handle out-of-fragmentainer-space situations.
We don't need special-code for when caption layout aborts because of
kOutOfFragmentainerSpace. Just leave it to the table layout algorithm,
which will call BreakBeforeChildIfNeeded() and handle this situation
correctly.
As it was, we could attempt to insert a break before the table, even
though the table had already produced fragments, which isn't allowed.
CL:3829930 was wrong in comparing the situation for table captions to
that for table cells. If this happens to cells, we DO need to propagate
kOutOfFragmentainerSpace to someone who can handle it (the table section
layout algorithm), since the table row layout algorithm lays out in the
inline direction.
Bug: 1375029
Change-Id: I3e53903004591922080338f88633b1b33c9890ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3959677
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1060136}
--
wpt-commits: 5ae18d5d2a019ea8421b2cfa4ece54e557b18ac3
wpt-pr: 36493
Automatic update from web-platform-tests
Add Duration Test to Ensure the Functionality of DurThreshold (#36137)
Add test with duration threshold and event duration to check if the
event that the performance observer receives has duration equals to
or greater than the duration threshold we setup.
Bug: 1368259
Change-Id: Ibc3232cad38f681d5d653f7fc01c2b9199f28986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3922116
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Han Gao <hangaoy@google.com>
Reviewed-by: Nicolás Peña <npm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1059400}
Co-authored-by: Han Gao <hangaoy@google.com>
--
wpt-commits: 96c883ecc0d911875b4c7e0238a20744a63218be
wpt-pr: 36137
Automatic update from web-platform-tests
Show complete server URL when starting server
--
wpt-commits: 74a4f4b724f07fb728b89ca0baa50081e40a6eb5
wpt-pr: 36494
Automatic update from web-platform-tests
[Multi Apps] Make list call forward compatible
Changed the list call to return a dictionary with app-ids as keys
which currently contains the app name in the values but can be
updated to contain more information in the future without breaking
backward compatibility.
Bug: 1171317
Change-Id: I36dbc0af78dd4a01d5a76d0c312274770c6aee5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3899114
Reviewed-by: Ivan Šandrk <isandrk@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Sam Thiesen <samicolon@google.com>
Cr-Commit-Position: refs/heads/main@{#1060001}
--
wpt-commits: 4c65973bb11b4ab053bc6f85e0d69bc58622e39a
wpt-pr: 36373