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
Automatic update from web-platform-tests
Add an anchor IDL attribute to <popup>, readonly for now
This CL exposes the anchor element as an IDL property. This will be
useful with the anchor positioning proposal (which isn't out yet).
Bug: 1168738
Change-Id: Ia47514dada57c44191c7af439b0051f3e3d26622
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2832148
Commit-Queue: Mason Freed <masonf@chromium.org>
Reviewed-by: Ionel Popescu <iopopesc@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#874440}
--
wpt-commits: db1033776685ff1793509a3be05c596acfa2821c
wpt-pr: 28567
Automatic update from web-platform-tests
Implement imperative slotting API changes
The original implementation of the imperative slot distribution
API was done before the final spec PRs landed. In the process of
landing those PRs, several changes were made to the way the API
works. Primarily, there are two changes:
1. The "auto" slotAssignment mode was renamed to "named".
2. The "linkage" that is created by HTMLSlotElement.assign() was
made more permanent. Previously, moving either the <slot> or
the assigned node around in the tree (or across documents)
would "break" the linkage. Now, the linkage is more permanent,
and the only way to break it is through another call to .assign().
See [1] for the chromestatus entry, [2] for the intent to ship,
[3], [4], and [5] for the spec PRs, and [6]/[7] for the landed spec.
[1] https://chromestatus.com/feature/4979822998585344
[2] https://groups.google.com/a/chromium.org/g/blink-dev/c/6U78F3KWJ78
[3] https://github.com/whatwg/html/pull/6561
[4] https://github.com/whatwg/html/pull/6585
[5] https://github.com/whatwg/dom/pull/966
[6] https://dom.spec.whatwg.org/#find-slotables
[7] https://html.spec.whatwg.org/#dom-slot-assign
Fixed: 1196842
Fixed: 1067153
Bug: 1067157
Change-Id: I0ee71043c23f3b49a1461296d722045f06eca540
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2824763
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874413}
--
wpt-commits: db1be04691e1b5fe58e186d682d26c69d282cbe0
wpt-pr: 28521
Automatic update from web-platform-tests
Consider text direction when building the GlyphData structure
When there is a list item we need to insert a space between the marker
symbol and the element being listed. We use the CreateForSpace function
in this case. Depending on the length, we create a space glyph of the
required font size, plus length - 1 0 width space glyphs.
The character index is added in a for loop as an ascending integer
sequence. However, this approach is not correct when the text is RTL,
where the index sequence should be descending to match how the text is
rendered visually.
Bug: 1188728, 1160582
Change-Id: I50c30ae142e73ffde3c3302b8e4baa4ab334a258
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2825447
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874326}
--
wpt-commits: c99958cd1ebbd17045842d57706545362616020e
wpt-pr: 28595
Automatic update from web-platform-tests
[LayoutNG] Nested fixedpos in a multicol static position
When a fixedpos is nested in an OOF inside a multicol, the static
position can be incorrect. The reason being that when calling
PropagateOOFPositionedInfo() from NGOutOfFlowLayoutPart, the offset
of the OOF ancestor should be relative the current builder
(i.e. the multicol container) rather than relative to its
fragmentainer. To fix this, adjust the OOF offset using the
fragmentainer offset so that it is relative to the multicol when
calling PropagateOOFPositionedInfo().
Bug: 1200324
Change-Id: I3742efe2daf38e3f51b8f4abc8c332b8de117385
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836226
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874309}
--
wpt-commits: 99e23355e8a04cb873e9cb6a0a3fe34fbd0d8125
wpt-pr: 28576
Automatic update from web-platform-tests
[Credentialless]: Test window.crossOriginIsolated (#28575)
This patch adds WPT test cases about whether COEP:cors-or-credentialess
allows a main document to be crossOriginIsolated or not.
COEP:require-corp and COEP:cors-or-credentialless have similar properties.
The only difference is one require no-cors response to include CORP
, the other strips credentials from those no-cors requests.
For everything else, they are perfects twins. In particular, they both
allow the document to be crossOriginIsolated.
Bug: 1175099
Change-Id: Ib03f68cc9849d9a2c5581175c299db8baf3226db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2835926
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874246}
Co-authored-by: arthursonzogni <arthursonzogni@chromium.org>
--
wpt-commits: 29e3e2928c1ac75e8a3a5a65ce0af21c3d616d15
wpt-pr: 28575
Automatic update from web-platform-tests
Remove Elements from toJSON
1. PerformanceElementTiming
2. LargestContentfulPaint
3. LayoutShiftAttribution
These include element or node in each toJSONForBinding implementation.
Those should be removed because they use the default toJSON operation and
those should not include interfaces that themselves do not have a toJSON
operation. So we should remove them from the toJSON builder and update
the existing toJSON WPT tests,
Bug: 1199954
Change-Id: I282439c17485264f1621102e3d002a693d48c1f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2831166
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874300}
--
wpt-commits: 0955b44aa165a247a43dd8ea6da9eb25b9012744
wpt-pr: 28559
Automatic update from web-platform-tests
NativeIO: Fix null pointer when throwing on releaseCapacity
This fixes a null pointer to the context when throwing on
releaseCapacity. Although the problem cannot happen for the sync case,
the corresponding logic is adapted to match the async case.
Bug: 1199639
Change-Id: Iaa7fd6d5bdcb3a616ba59f7c419b11203c293e67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2831590
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Richard Stotz <rstz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874298}
--
wpt-commits: 77ca851359d5bcc5e7c40168b6473bea51de4daa
wpt-pr: 28546
Automatic update from web-platform-tests
Move audioparam-nominal-range test to WPT
The test audioparam-nominal-range verifies that the nominal range
(min/max): of each AudioParam has the specified values, and that
attempts to set the value outside the min/max range clamps the value
to the nominal range.
The behavior is specified here:
https://webaudio.github.io/web-audio-api/#nominal-range
Bug: 1041105
Change-Id: I03f58e3e29aaeff84d764fedd6748fe41baf6eeb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836870
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874293}
--
wpt-commits: b65ba2471f6f8356e606470f9837bde04e5d3122
wpt-pr: 28600
Automatic update from web-platform-tests
[selectors] Add test for :focus-visible and Shadow DOM
This test check that :focus-visible doesn't match on the ShadowRoot,
otherwise UAs would end up showing two focus indicators.
--
wpt-commits: aba7d28837d13947d561337c762e4de8ff9feea6
wpt-pr: 28131
Automatic update from web-platform-tests
Fix padding-valid.html to use sorted calc() in expected serialized value according to spec
https://drafts.csswg.org/css-values-4/#sort-a-calculations-children
> 11.13. Serialization
> [...]
> 6. If root is a Sum node, let s be a string initially containing "(".
> Sort root’s children.
--
wpt-commits: 2dca9ad3b16faeed9c82d80084a7323735c5821a
wpt-pr: 28598
Automatic update from web-platform-tests
Tests for unbounded cue end time (#28394)
Added tests for unbounded TextTrackCue endTime changes proposed in whatwg/html#5953 & w3c/webvtt#493
--
wpt-commits: 786c430165d916bdab740ab491ac541afb3f8bf5
wpt-pr: 28394
Automatic update from web-platform-tests
[idlharness.js] avoid overtesting the non-exposure of interfaces (#28594)
These tests are being generated for dependencies that shouldn't be
tested because |this.untested| wasn't checked in this case.
--
wpt-commits: f6b9f5ead14104b65f1ab6bcf505214f30a71e7e
wpt-pr: 28594
Automatic update from web-platform-tests
[ReadableByteStream] Handle enqueuing when detach
Attempting to call enqueue() on a ReadableByteStreamController after
controller.byobRequest.view.buffer had been detached would crash with a
null pointer dereference.
Make it throw an exception instead.
BUG=1200302
Change-Id: I86b1511ef154a42ca78271618e00d8e1c5e6ae5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836768
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874225}
--
wpt-commits: 5233fe69580d5d5d10e46869958093ea771a743f
wpt-pr: 28586
Automatic update from web-platform-tests
Fixed crash for nested removals for datalist
The case where we did a remove in the subtree already being removed, was
handled for style traversal roots. For the datalist element, the nested
removal does not necessarily happen in the same subtree. That means the
traversal root update in the outer removal would not necessarily work.
Instead, just fall back to the document root as the traversal root.
Bug: 1199861
Change-Id: Id95f3e7b1010f46183c0f9d1223e6726b29f0fe4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2835850
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874219}
--
wpt-commits: 8d209fd8808d3f57c20de7000dbd17bae6fea9c4
wpt-pr: 28573
Automatic update from web-platform-tests
Have fetch streaming upload tests to run with HTTP/2 (#28236)
Move the test cases to request-upload.h2.any.js.
Whether we want to support streaming upload for HTTP/1.1 is
being discussed, and we may end up adding similar tests for
HTTP/1.1 later.
--
wpt-commits: 0573c1bd843d06def127be06833985b083213ada
wpt-pr: 28236
Automatic update from web-platform-tests
[TablesNG] quirks mode proposals
There are a couple of quirks that only FF implements.
I propose modifying the spec, and depreciating the quirks.
Change-Id: Id73a73e152b7f1557a236e4f3c7393fed52f4927
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836834
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874174}
--
wpt-commits: 51b49f2786e2a998cb292b90aaf0b89dd0166ca9
wpt-pr: 28583
Automatic update from web-platform-tests
[TablesNG] Tentative element sizing
Just confirming what spec says in this one.
Change-Id: I18ad4a726330dc3be58b08ce25aa36c2f9e171ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836871
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874166}
--
wpt-commits: 4eda604bed2bc55ba832319ed602d2e003949c6d
wpt-pr: 28581
Automatic update from web-platform-tests
[composite-bgcolor-animation] Handle non-replace keyframes
Currently we check whether the animation's composite mode is replace
nor not, if not, we fallback to run the animation on the main thread.
But we should actually check whether there is any keyframe that
is non-replace. This CL fixes that.
Bug: 1200450
Change-Id: Ic58f37bb4e94f1ca06cc4ff2a86f8a73f394d06b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2836907
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874098}
--
wpt-commits: c0bf8e31d482eb6456dd9772651f7b0c76462fd0
wpt-pr: 28584
Automatic update from web-platform-tests
Add more JSON modules tests
Add JSON modules tests to validate the following:
- Cross-origin imports fail without the
Access-Control-Allow-Origin response header.
- The crossOrigin CORS policy is respected
- referrerPolicy is respected.
These tests aren't as fully comprehensive as the corresponding tests
for JS modules under
external/wpt/html/semantics/scripting-1/the-script-element/json-module.
That level of redundancy is probably not particularly valuable, since
JSON modules and JS modules should share the same codepaths for these
features. The intent of these tests is to validate that implementations
are indeed using the same codepaths for JSON modules as for JS modules,
so that these features work the same for both module types.
Bug: 1132413
Change-Id: I07e2ad2e1afc14070ddef5f95ff2f65e147ec9a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2824897
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#874087}
--
wpt-commits: 8add836e2aaeb423c8d22f9b131a0c6b1815787b
wpt-pr: 28489
Automatic update from web-platform-tests
[ImageDecoder] Treat kNoImage after data completion as an error.
If the decoder fails to decode anything after we've received all
data this should be treated as an error. Failure to do so can
lead to out of order processing and promises never resolved.
R=eugene
Fixed: 1200137
Change-Id: Ia88bf7f6acd3d6df092ded66c7a8df162d2e9d18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2837480
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874064}
--
wpt-commits: 9de16442c812a5dc2411a288bd141ed80b0aa251
wpt-pr: 28589
Automatic update from web-platform-tests
Add initiallyopen attribute to the <popup> element
This add an attribute called initiallyopen to the <popup> element.
When this attribute is present on page load, the first such element
will be shown by default.
See [1] for the conversation and Open-UI resolution.
This CL also re-points the explainer links for all popup tests
to the new Open-UI repo.
[1] https://github.com/WICG/open-ui/issues/311#issuecomment-820655960
Bug: 1168738
Change-Id: Ib95d12234f359d503dc168e6799dd2a17b0dc18e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2832157
Reviewed-by: Ionel Popescu <iopopesc@microsoft.com>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874037}
--
wpt-commits: 9144cfb5bfbeaa6f919bd02ebe53ccbbd408beb4
wpt-pr: 28566
Automatic update from web-platform-tests
Always reinitialize decoders after Flush().
This is the expected behavior for media decoders, so for now we
should copy it to avoid surprising issues.
R=eugene, sandersd
Fixed: 1199245
Change-Id: I5d2a8f55795607f7fce199cf15e58f9c79e56678
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2828477
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#874023}
--
wpt-commits: a6a7c84620a5388cfce27fb6f1eab6fad716fdde
wpt-pr: 28530
Automatic update from web-platform-tests
[composite-bgcolor-animation] Composite no-op animations
Please refer to the discussions here:
https://docs.google.com/document/d/1HtnP6oNFvcYIn91tHPhQR5n_8zhWLHfG_eXi4HG8Pzc/edit
On the above notes, we have reached conclusions that:
1. It is OK to run a no-op animation on the compositor thread. In
this CL, we let a no-op background-color animation run on the
compositor, which is consistent with transform and opacity.
2. For background-color animation cases, when we try to create a
compositor animation + we found that the layout object doesn't
have a UniqueId, this implies that it is a no-op animation and
we give a special ElementId to the CompositorKeyframeModel. Then
when we tick the animation on the compositor side, we can short
circuit it such that we don't need to update the animated property
value because it is a no-op animation.
Bug: 1193757
Change-Id: I1a6b4d91c106ae830550e54f451d0cdf5dea9721
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2795243
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#873969}
--
wpt-commits: 4e2b9701813d4d49d397783b9d92009658651dee
wpt-pr: 28317
dependabot[bot]
Yi Xu
moz-wptsync-bot
Dale Curtis
Matt Wolenetz
Mason Freed
davidsgrogan
Javier Fernández García-Boente
Alison Maher
Blink WPT Bot
Toshiaki Tanaka
Richard Stotz
Raymond Toy
Mike
Manuel Rego Casasnovas
Tim Nguyen
Rob Smith
Philip Jägenstedt
Adam Rice
Luca Casonato
Rune Lillesveen
Yoichi Osato
Yifan Luo
Aleks Totic
Xida Chen
Daniel Clark