Automatic update from web-platform-tests
Add JSON module test for load and error events
Add a test validating that the load event fires when appropriate for
a <script> element containing a JSON module import. Also check that
the error event is fired when a JSON module 404s.
These aren't intended to replicate the full suite of corresponding
tests for JavaScript modules. The purpose is to serve as a check that
implementers are reusing the codepaths for these events when
implementing JSON modules.
Bug: 1132413
Change-Id: I4277411c1f1f758c9ea163f87c2a539eacabe082
--
wpt-commits: 161110d01cafe02ac369cbcf205a49dd528305bc
wpt-pr: 28633
Automatic update from web-platform-tests
Add fuzzy matching to transform-input-015.html
external/wpt/css/css-transforms/transform-input-015.html is failing due
to anti-aliasing. Fix this issue by using fuzzy matching on 2 pixels.
Bug: 1051143
Change-Id: Ie60f02f95bcdaee7c26884c1dd2ec128df60f014
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2844766
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#875355}
--
wpt-commits: aaf4be7517225472afa14d2e7464ceb3562f3123
wpt-pr: 28651
Automatic update from web-platform-tests
Add JSON modules tests for charset, integrity, and MIME type parameters
Add JSON modules tests for the following:
- The <script> element's integrity attribute is respected.
- JSON modules are always decoded as UTF-8 regardless of Content-Type
or the document's encoding. The existing coverage we had on this in
utf8.tenative.html was renamed to charset.html, refactored, and
expanded.
- Adding parameters to the MIME type doesn't prevent it from being
evaluated as a JSON MIME type.
Note, some of the existing MIME type tests for */*+json still fail
because it seems the spec issue on these at
https://github.com/whatwg/mimesniff/issues/112 hasn't been fully
resolved. I'll follow up with that separately.
Bug: 1132413
Change-Id: I682de01bbb14b53214fcc16f427a4875f8cfed7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2841103
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#875274}
--
wpt-commits: cda427384ac75751fe809c6006ca5167e0c8f7ad
wpt-pr: 28606
Automatic update from web-platform-tests
[LayoutNG] Nested fixedpos in nested multicol w/ CB in outer multicol
Nested fixedpos elements in a nested multicol were handled previously
by CL:2791850 and CL:2823871. However, if a fixedpos was nested in an
OOF element inside a nested multicol, and the containing block for
the fixedpos was in an outer multicol, the fixedpos was never laid out.
The reason being that when we add an inner multicol with pending OOFs,
we don't make any changes to its OOF descendants. So if the fixedpos
containing block existed outside the inner multicol but inside the
outer multicol, fixedpos_containing_block in NGOutOfFlowPositionedNode
would never be set.
In order to fix this, we need to store a fixedpos_containing_block along
with any inner multicols with pending OOFs, if one exists. A new
struct, NGMulticolWithPendingOOFs, was added to store this information.
The fixedpos_containing_block gets set the first time the inner multicol
reaches a potential fixedpos containing block.
The multicol_offset variable of NGMulticolWithPendingOOFs was added for
two purposes:
1. Similarly to CL:2836226, the static position was incorrect for
nested fixedpos elements in a nested fragmentation
context, and whose containing block was outside both multicols.
(See fixed-in-nested-multicol-with-transform-container.html for an
example).
In this case, multicol_offset is the accumulate multicol offset
relative to the outer fragmentation context. This gets added
to the static pos of any fixedpos descendants in
NGContainerFragmentBuilder::TransferOutOfFlowCandidates().
2. In the case where the inner multicol found a fixedpos containing
block, multicol_offset will be the offset from the multicol
to the top of the fixedpos containing block. This is also used
in NGContainerFragmentBuilder::TransferOutOfFlowCandidates() to
ensure that the fixedpos static position is correctly updated.
MulticolCollection was updated from a HeapHashSet of inner multicol
LayoutBoxes to a HeapHashMap from inner multicol LayoutBoxes to
NGMulticolWithPendingOOFs.
In order to avoid creating two NGMulticolWithPendingOOFs structs (one
for the logical space and one for the physical space), the
NGContainingBlock struct was also updated to a templated struct.
Note: this CL does not handle the case of more than two layers
of nesting. For example, in the following case, the fixedpos would
not be laid out at the correct offset:
multicol
multicol
transform
multicol
relpos
abspos
fixedpos
In order to get this case working, we'd also need to store a reference
to the multicol that the fixedpos containing block was found in inside
NGMulticolWithPendingOOFs. However, this use-case doesn't seem worth
handling at this time.
Bug: 1198674,1200324
Change-Id: I213c35514fecf84fc62e55fe5531cff8b0830429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2844299
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#875257}
--
wpt-commits: 99efbde7f07b6d1b8e6a7708e99c592689451c3d
wpt-pr: 28634
Automatic update from web-platform-tests
Fix sharedarraybuffer.html web_tests
Move the test to WPT and use a crossOriginIsolated context to allow
constructing SharedArrayBuffer.
Bug: 1194557
Change-Id: I4661a6c1b54479779367f0cb273dcd4f5fe3cf34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2845404
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875204}
--
wpt-commits: f0100ca251375fc5bf241d14ceaf6dbef74432e9
wpt-pr: 28643
Automatic update from web-platform-tests
Add a lint that checks paths are unique irrespective of case
Paths that are the same excluding case don't work reliably across
operating systems and can be forbidden by vendor CI. So we should
error on these paths in the lint.
--
wpt-commits: ff952d5fb2b0879138f24c89e4b190d8a46d8d57
wpt-pr: 28396
Automatic update from web-platform-tests
[Credentialless] Add tests for service worker.
This CL add tests for service worker with COEP:cors-or-credentialless on
frames COEP:none and COPE:cors-or-credentialless and send same/cross
origin requests from the workers with no-cors mode.
Cookies from same_origin should be remained while cookies for cross_origin
request should be removed.
Bug: 1199282
Change-Id: I5043c4092c3562dbefe222b93e1e5c6a8728f259
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2827857
Commit-Queue: Yifan Luo <lyf@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875092}
--
wpt-commits: 7b487b65fcd70f6c95d7dbfbf6a5466a2b6be646
wpt-pr: 28516
Automatic update from web-platform-tests
Add a WPT for WebTransport constructor
Also remove a test for QuicTransport constructor since it is no longer
supported.
Bug: 1201569
Change-Id: I76e5ea6a9a109f03f18d42f2ec359f8974998e5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2846261
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875063}
--
wpt-commits: 66485c70576bd185df5d24e4146d31c024a42ba2
wpt-pr: 28636
Automatic update from web-platform-tests
Pixel-snap 'background-clip' ('content-box' and 'padding-box')
The actual painted background is snapped so this should make the two
consistent.
Bug: 957946
Change-Id: I297543a64ab58f854ed3d7bf35bfe8555b3a0993
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2840843
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#875058}
--
wpt-commits: c842a593ec65ac8c6680f1b24d2c37666975e478
wpt-pr: 28629
Automatic update from web-platform-tests
Merge xslt/ into dom/xslt/ (#28639)
After https://github.com/web-platform-tests/wpt/pull/28638 the interface
is in dom.idl, so remove xslt.tentative.idl and move the remaining tests
into dom/xslt/ with a new README.
--
wpt-commits: f50fad694e04166f60af738d91114b65757df050
wpt-pr: 28639
Automatic update from web-platform-tests
CSP: Move form-action check to the browser
The Content Security Policy check for 'form-action' is a navigational
check, that we perform at the moment half in Blink (for the initial
URL) and half in the Browser (for redirects). The Browser part is
currently implemented in a navigational throttle and is not using the
correct policies and context.
Thanks to the PolicyContainerHost, this CL simplifies the check in the
Browser by removing the FormSubmissionThrottle and moving the check to
the NavigationRequest, in the same place where other navigational
checks are performed. At the same time, it removes the check from
Blink relying to the Browser check also for the initial request URL.
Change-Id: I28be978be3c86f1d8ad8b41398542c4e735758e3
Bug: 694525,663512,700964,1172898,1021462,713388
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2797339
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875047}
--
wpt-commits: ae2b12963e524582555638df74e7a287d35aa048
wpt-pr: 28502
Automatic update from web-platform-tests
[idlharness.js] remove support for implements statements (#28619)
The last of these were removed in https://github.com/web-platform-tests/wpt/pull/17060.
--
wpt-commits: 684b773116541669815c55c1e3e70b3dc8890250
wpt-pr: 28619
Automatic update from web-platform-tests
[ImageDecoder] Remove decodeMetadata() in favor of tracks.ready.
Since metadata is always queued automatically, decodeMetadata()
doesn't really do what it says. There's a better web idiom for
this a 'ready' property that's a one-time resolved promise.
Instead of calling decodeMetadata(), clients should just use
decode.tracks.ready.then(...)
Since the last round of breaking changes didn't cause any
issues without a deprecation period, drop decodeMetadata()
without a deprecation period as well.
Fixed: 1182435
Change-Id: I95317d6daaba9a98a7f33d594b50921800a6fbe3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2842034
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874987}
--
wpt-commits: 33c7cb54285ac9dc5161a5b7cf24690723397911
wpt-pr: 28612
Automatic update from web-platform-tests
Removed scroll start and end offset properties of ScrollTimeline
Made modifications spec'ed in
https://github.com/w3c/csswg-drafts/pull/5803:
- Removed startOffset and endOffset attributes.
- Updated procedures based on spec changes, including allowing single
scroll offset of 'auto'.
Bug: 1094014
Change-Id: Id08c9ce1818bd561ac291ca3e1f99c22dbb15674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2801290
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874955}
--
wpt-commits: 44d0f24ba4dc413c7142bdb7d1daf9186bbd680d
wpt-pr: 28358
Automatic update from web-platform-tests
Split the test cases for mapping width and height to aspect ratio (#28623)
Split up the test cases for mapping width and height attributes to aspect ratio.
To make sure that each element has its own test case, so that the test won't
break in the middle of test cases and affect other images' test.
--
wpt-commits: 1f07a2242db1842f57c321489bf24c51225522cf
wpt-pr: 28623
Automatic update from web-platform-tests
Don't try to set Access-Control-Allow-Origin to None in worklet tests
--
wpt-commits: cac1166c49e3aa511f8fd38ce0a5f588f9f145d4
wpt-pr: 28625
Automatic update from web-platform-tests
[composite-bgcolor-animation] Move some layout test to subdir
Some of the test in css-backgrounds/animations/ are specifically
test that we can trigger repaint or paint invalidation correctly.
This CL moves those test into a subdir. No behavior change is
expected.
Bug: 1197218
Change-Id: I7e585dae9316a19cfbe08ba264b353eca5b21934
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2842187
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874766}
--
wpt-commits: 8d09bbcbe986725e7f9b770c4443a2a598ee59a3
wpt-pr: 28624
Automatic update from web-platform-tests
[WebCodecs] Fix WPT tests for reset during flush.
The previous test didn't actually expose the desired issue since
flush() was still pending when reset() occurs. Resulting in the
flush() being cancelled before it started executing.
Instead wait for the first frame before queueing the flush to
ensure there are no other pending operations.
R=eugene
Fixed: 1200768
Change-Id: I8a68ef608aa5565f9c86f8c004c292298d30ef0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2841756
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874747}
--
wpt-commits: f13c3c022ac45ee6bd282af0be7fc7d730e9c9f5
wpt-pr: 28613
Automatic update from web-platform-tests
Off-thread CSS paint: handle no-op animation
In a previous CL here:
https://chromium-review.googlesource.com/c/chromium/src/+/2795243
We handled a no-op background-color animation by keep it running on
the compositor thread. This is okay because it is a no-op animation.
This CL follows the same approach as the background-color animation
case. In particular, when it is a custom property animated by CSS
paint worklet, and this custom property animation is a no-op one,
then we keep it running on the compositor thread.
Bug: 1193162
Change-Id: I3f2093092053ad9c9363a64d6d46df039e9bddf0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2841783
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874704}
--
wpt-commits: b47b8a1f933a9ec2b62f1608886155f911431111
wpt-pr: 28605
Automatic update from web-platform-tests
[GitHub Actions] consistently use ubuntu-20.04 and checkout v2 (#28538)
The default fetch-depth has changed, and the epochs workflow needs the
history for `./wpt rev-list` to work.
--
wpt-commits: 280d5059bbeff7177215e0990d7cfb3ef8e14ec7
wpt-pr: 28538
Automatic update from web-platform-tests
[GitHub Actions] Update certificate regeneration workflow (#28548)
For consistency of naming and versions in other workflows.
--
wpt-commits: a5a57f829bc30ca1e8a637df61a551603f6c6365
wpt-pr: 28548
Automatic update from web-platform-tests
Historical test for WheelEvent#initWheelEvent
--
wpt-commits: df6f7468721aa6c498ce42281ab4c2cb33066259
wpt-pr: 28241
Automatic update from web-platform-tests
Only clip the axes that should be clipped, also when block-fragmented.
Bug: 829028
Change-Id: I02c3c7be4b82c7213c96a6413e9a5aa0dc50cd9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2837827
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874610}
--
wpt-commits: 4d03b26e10d8565bb10b27b0fd3c9aa518c0d18e
wpt-pr: 28602
Automatic update from web-platform-tests
[blink] 1/2 Module streaming compilation for <link rel=preload>
Share ScriptResources, even if the script type mismatches to avoid
downloading resources twice in the case of preload for class and
module scripts.
Bug: 1178198
Change-Id: I32feadfdd04ce3cabae30a2208d9daedb4724380
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2764608
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874609}
--
wpt-commits: de1d31decb9c7f9fdcd77a9c553b4f3d49e6f061
wpt-pr: 28116
Automatic update from web-platform-tests
Adding more toBlob and toDataURL tests for p3 colorspace
Adding toBlob and toDataURL tests for p3 colorspace, which does the
following:
- create a p3 canvas
- Use putImageData to put in some p3 data
- Call getImageData to retrieve data from canvas
- call toBlob/toDataURL and asking for data in p3 format
- compare if result of toBlob/toDataURL is same as the result from
getImageData from step 3
Bug: 1178707
Change-Id: I720b881defea6c94ab900499a6589d29323b1457
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836407
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: Juanmi Huertas <juanmihd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874588}
--
wpt-commits: ae3e3fc88e738e6ea434f5f877a91223832e6f97
wpt-pr: 28587
Automatic update from web-platform-tests
[WebCodecs] Fix issues when reset() happens during flush().
reset() clears the active configuration, so we should not attempt
to reinitialize if reset() was called during flush().
R=eugene
Fixed: 1200768
Change-Id: Iac34480ba859ab156d6a93c943a7ffce9304b1ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2842784
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874546}
--
wpt-commits: 48d3f81aaa869cfeb088cec66b50b513319bf2ec
wpt-pr: 28609
Automatic update from web-platform-tests
MSE-in-Workers: Add tests of detach concurrent with appendBuffer
To help find faults like those fixed in crbug 1195441, this change adds
a web test that is like the existing
mediasource-worker-play-terminate-worker case, though instead it
detaches the MediaSource from the element at various times before,
during and after the worker is buffering in small pieces. Further
refinement of the MediaSource readyState for the scenario where a
concurrent "closing has begun" causes exception on attempt to use the
closing MediaSource will be necessary to refine this new test further to
not ignore so many exceptions in the worker thread; TODOs are included
for that in the new test.
This change also refactors MSE-in-Workers tests' communication to use
a structured message format.
BUG=1195441,878133
TEST=mediasource-worker-detach-element.html, confirmed locally in a
release build with DCHECKS enabled to reliably catch the issue in bug
1195441 (with that bug's fix locally reverted for this check).
Change-Id: I3e041d7b06db96d3d976593f20181d073fad1da1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2823974
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Reviewed-by: Will Cassella <cassew@google.com>
Cr-Commit-Position: refs/heads/master@{#874470}
--
wpt-commits: ece50720e2ad03fb16c129e50706dd77029d4ca4
wpt-pr: 28491
