Automatic update from web-platform-tests
Roll WebGPU CTS
Roll in copyImageBitmapToTexture cts
Change-Id: Ie4ddf5f7dad5fa6487cbaedc5ca78e6e1d448602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986630
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#729235}
--
wpt-commits: 527a9287825118957bb7d94c098c448cef9d6982
wpt-pr: 21043
Automatic update from web-platform-tests
MediaRecorder: Implements spontaneous stopping.
When all recorded tracks have ended, the MediaRecorder should spontaneously
stop and invoke onstop(), according to
https://www.w3.org/TR/mediastream-recording/#mediarecorder-methods.
This change implements this previously unimplemented feature.
Bug: 1013590,1035454
Change-Id: Ia96fa56f8ef20ff347822591c01703bfb276072b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969577
Commit-Queue: Markus Handell <handellm@google.com>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#729067}
--
wpt-commits: 3785c85141a5595ace07703b63ff2f092651b546
wpt-pr: 20865
Automatic update from web-platform-tests
Add tests for cookies' `Domain` attribute.
The current WPT suite for cookies' domain attribute is quite broken; we
did a bad job porting it. This patch adds tests for the specific case
called out in https://github.com/httpwg/http-extensions/issues/238,
and described in https://tools.ietf.org/html/rfc6265#section-5.2.3.
Change-Id: Ib8614d5834e028cfc093594b22bc7c8cb4f086a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1983228
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728947}
--
wpt-commits: fee0bc6757220fed75e3a5e286bcdafea0849575
wpt-pr: 20934
Automatic update from web-platform-tests
[Trusted Types] Should not throw error if default createXYZ policy is empty under report-only.
Bug: 1008022
Change-Id: I3e9d867eb354c518cf03b931b30c3df1d313d6c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985925
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Commit-Queue: Yifan Luo <lyf@google.com>
Cr-Commit-Position: refs/heads/master@{#728902}
--
wpt-commits: a74e1f57038e8cb818c2feb9cd879e540d50fcc1
wpt-pr: 21027
Automatic update from web-platform-tests
[css-grid] Exclude implicit grid tracks from the resolved value
https://github.com/w3c/csswg-drafts/issues/4475 resolved to try to stop
including implicit tracks in the resolved value of grid-template-columns
and grid-template-rows.
This implies that the resolved values will have less information now,
which affects lots of tests. I have edited them depending on the case:
- When the size of the track was irrelevant (e.g. just checking whether
some value was syntactically valid), I have just updated the expected
value.
- When the size of the track was relevant, but it wasn't important for
the tracks to be implicit, I have made them explicit in order to get
the same value.
- When the test was about the sizes of implicit tracks, I have added
new checks for the size and position of the grid items.
Intent to Implement and Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/EKvyx2lZJXI
Spec: https://drafts.csswg.org/css-grid/#resolved-track-list
Bug: 1024927
Change-Id: I4677c184be263eaab08d4aee95bb868306d58228
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897931
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#728894}
--
wpt-commits: a5ef60f36a5d3a4e2c6903648a20296205c42725
wpt-pr: 20327
Automatic update from web-platform-tests
[css-pseudo] Test dynamic 'list-style-position' for nested ::marker
marker-content-013.html was already testing that various kinds of list
markers are properly updated when 'list-style-position' changes.
However, nested ::marker originated by a ::before or ::after were not
included. I'm working on a patch that could have broken that case, so
covering it in the test seems a good idea.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-013.html
Change-Id: I99c72c02298372c2d026adea99fb580a9bc8890a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985951
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728868}
--
wpt-commits: 2716d92b9325da7076d37d1b048d76ced69a269d
wpt-pr: 21058
Automatic update from web-platform-tests
Don't try to use blobs as CanvasImageSource for OffscreenCanvas tests
Several OffscreenCanvas tests try to directly pass the result of an
XMLHttpRequest directly into 2d canvas context functions that take
CanvasImageSource as an argument. As blob is not a valid CanvasImageSource,
these tests all fail with TypeError. This fixes issue #20867.
--
wpt-commits: d1b00400ea0cd9576809049c86689211000ace50
wpt-pr: 20886
Automatic update from web-platform-tests
html: add invalid pattern tests for patternMismatch
--
html: add Unicode regex test
--
html: Test <input type=email multiple> for patternMismatch
See https://html.spec.whatwg.org/C/input.html#the-pattern-attribute for
the special treatment of email-state <input> elements with multiple
attribute.
--
wpt-commits: 63900745f72fe10017de96b63179bc3c283d90b8, a5d9d2c94ff76d5c9e5c5b53f225d9dbab514f31, 84241672c183678a31c2ec8940556e4dd47270db
wpt-pr: 21060
Automatic update from web-platform-tests
Revert "Fix toJSON in WindowPerformance and PerformanceResourceTiming"
This reverts commit 400050e6ae3d44a540786d89314419a0f8427d88.
Reason for revert: Failure on WebKit Linux MSAN
https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20MSAN/3734
[3153/4358] external/wpt/uievents/idlharness.window.html failed unexpectedly (test timed out)
Original change's description:
> Fix toJSON in WindowPerformance and PerformanceResourceTiming
>
> Per https://heycam.github.io/webidl/#es-default-tojson, it is correct to
> directly add the attribute values of the interface to the builder
> instead of adding the results of toJSONForBinding().
>
> Change-Id: I07f7ee5992de59938c0116f90dc4b5229c5d6e9d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982792
> Reviewed-by: Jeremy Roman <jbroman@chromium.org>
> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#728540}
TBR=jbroman@chromium.org,npm@chromium.org
Change-Id: I06ebf62eb1217de6e7241b4c3ffa6a77d2c696da
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986572
Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728775}
--
wpt-commits: 73d748fca7e82ecdd0c41c780090c4f0be5b6245
wpt-pr: 21061
Automatic update from web-platform-tests
Constructable StyleSheets: Assert that empty title is null, rather than empty string (#21035)
--
wpt-commits: e3d98e8f0cd202a5b2c5d5cac3302c432557a474
wpt-pr: 21035
Automatic update from web-platform-tests
Fix submit buttons with children that get removed
If a <button> element inside a <form> has a child element which is
clicked, and the <button>'s onclick handler removes the child element
from the DOM, the <button>'s default event handler which submits the
form is never called.
If this happens, and the <button>'s onclick handler also manually
submits the form via form.submit(), then the form double-submit fix made
in crrev.com/c/1850358 will prevent form.submit() from submitting the
form because the form.submit() is blocked until the <button> gets the
DOMActivate event, which never happens if the child element is removed
from the DOM before it can emit the DOMActivate event to the parent
<button>.
This patch will submit the form in this case by listening to the click
event instead of the DOMActivate event. If the click event is
additionally preventDefault()ed, this patch will not cover that case.
Once we switch back to async form submission in crbug.com/1013385 then
all of the cases will be covered and this patch will be reverted.
Bug: 1037740
Change-Id: I04cdff451b363b5fafa26d2c58ec0aa76ed95a0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1983547
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728662}
--
wpt-commits: e5033e408e557bbd30560fa5aaf96cadb06c3926
wpt-pr: 20945
Automatic update from web-platform-tests
Fix invalidation of resizer when container's paint offset changes
Add the container's paint offset to resizer's visual rect to ensure
correct invalidation on change of paint offset.
Bug: 1036824
Change-Id: I4fc5caa2364c62d415dd54cb54f42bdca525ea81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986431
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728603}
--
wpt-commits: ae32337b9660e01d5c497dbcbc2ce5935a067085
wpt-pr: 21037
Automatic update from web-platform-tests
DOM: simplify document.createEvent() test
This removes and simplifies a conditional that were hard to parse.
--
wpt-commits: eb55d6105892b783a8bfeb3a34b251171fe2228b
wpt-pr: 21053
Automatic update from web-platform-tests
Fix toJSON in WindowPerformance and PerformanceResourceTiming
Per https://heycam.github.io/webidl/#es-default-tojson, it is correct to
directly add the attribute values of the interface to the builder
instead of adding the results of toJSONForBinding().
Change-Id: I07f7ee5992de59938c0116f90dc4b5229c5d6e9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982792
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728540}
--
wpt-commits: 28a0dbc314b942c1a7ace3b5befb2f67c8a70481
wpt-pr: 21036
Automatic update from web-platform-tests
DOM: rename nuked to removed in historical test
--
DOM: document.origin is historical now
For https://github.com/whatwg/dom/pull/815.
--
wpt-commits: 9daea0098bc3f35f0f0d9ee6e970223dc8187384, c9ea677557badbf83258f5e384bf9d3c0efb62cf
wpt-pr: 20995
Automatic update from web-platform-tests
Ensure .ini files are never detected as tests
This suffix is reserved for metadata files
--
Fix argument unpacking for crashtests in webdriver executor
--
wpt-commits: dbf883768642c48337a6051dbbe5b786ddc1bd68, bba41778ac81ed22b1c859ce80e368560e9f9caf
wpt-pr: 21051
Rather than change the expectations here I should have marked Firefox as failing
the checkMute tests as the behaviour is at least partly incorrect.
Differential Revision: https://phabricator.services.mozilla.com/D59165
--HG--
extra : moz-landing-system : lando
Enabling the pref here should help us catch regressions to the RTCP bye / timeout
mute code even though we leave it disabled overall.
Differential Revision: https://phabricator.services.mozilla.com/D59164
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
HTML: attempt to make COEP test less flaky
Hopefully addresses https://bugzilla.mozilla.org/show_bug.cgi?id=1605382.
--
wpt-commits: e8fdcbaf22bf28238bb126d84bc960fe9625fe02
wpt-pr: 21021
Automatic update from web-platform-tests
[webnfc] Add several wpt tests
This CL adds several wpt tests for Web NFC:
- Test push operation fails when data transfer fails
- Verify pushed message for empty record type
- Test reading message with multiple records should succeed
Bug: 520391
Change-Id: Iadb13f6cebaf30514ba7bef65a69302b368e4359
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982271
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#728434}
--
wpt-commits: 3488a5a845bec08943f66974e9f0df4ffe96774a
wpt-pr: 20921
Automatic update from web-platform-tests
Revert LayoutInline::CollectLineBoxRects
This patch reverts |LayoutInline::CollectLineBoxRects| not to
use |NGInlineCursor|, by manually merging parts of r706815
<crrev.com/c/1862534> and r710694 <crrev.com/c/1888624>.
|NGInlineCursor| is rapidly changing that reverting is not
easy. This patch reverts not to use it for |getClientRects|
and a few other callers.
Testing more on culled inline box indicates that the phase 1
of LayoutNG regressed some cases from legacy, and
|NGInlineCursor| work regressed further. We might want to fix
when NGFragmentItem ships, but better not to change the
behavior until then.
Bug: 1036358
Change-Id: I47a60f5d3a505d4b43eba0d8b5adc64e02cbcd28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971632
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728433}
--
wpt-commits: 280816c7465a6593f06f9f5651a70eb857f9f774
wpt-pr: 20892
Automatic update from web-platform-tests
Fix validity.valueMissing tests (#21031)
These changes fix expectations for validity.valueMissing and validity.valid for disabled/readonly textual elements. This fixes#21007.
--
wpt-commits: 31e82ba312dea8b0011237fd696d3c87c2015d65
wpt-pr: 21031
Automatic update from web-platform-tests
Use mozlog logger in FontInstaller
This is the right thing to do, and prevents a race where we try to log
after the stdout capture queue is closed
Differential Revision: https://phabricator.services.mozilla.com/D56567
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1598561
gecko-commit: 2a0e33dbb9c83f2444361497e86e7af7d69fef44
gecko-integration-branch: autoland
gecko-reviewers: maja_zf
--
Remove unused import
--
wpt-commits: fd7d1aaf7d490d8d0e9f039db02a530891112c5a, d24e7e551416c0adb313fd51070c6db4762949b8
wpt-pr: 20997
Automatic update from web-platform-tests
Handle multicol intrinsic inline-size changes.
This was broken both in legacy multicol and with
LayoutNGBlockFragmentation.
Legacy: We stored the intrinsic size in the column sets, in addition to
in the flow thread. There was no good reason for this, and it caused
trouble once something caused the intrinsic size of the multicol
container to change, since the column sets would never be marked dirty
again. Just set the intrinsic size of column sets to 0 to fix this.
LayoutNGBlockFragmentation: The flow thread is still created even if NG
block fragmentation is enabled, but the flow thread is invisible to NG,
so when calculating the intrinsic size of nodes in a subtree, we'll skip
the flow thread - which means that it will never be marked clean. Skip
to the containing block of the flow thread when marking preferred
logical widths dirty.
This fixes the remaining part of the demo in bug 1037790 - when trying
to reduce column-count to 1. Without this fix, the multicol container
would remain too wide.
Bug: 1037790
Change-Id: I89c7cbeb3132162b6c52ae30e98a0da21cd34ef1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985770
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728401}
--
wpt-commits: e30880f3341ca022f7009af13eb871872d02caaf
wpt-pr: 21009
Automatic update from web-platform-tests
Recalculate flow thread intrinsic size when parent needs it.
If the multicol container gets marked for intrinsic size recalculation,
its flow thread child might need to recalculate its intrinsic size as
well (the intrinsic inner size of a multicol container is stored in the
flow thread), although it may not have been marked as such. This
situation occurs when column-count changes.
Re-use the NeedsPreferredWidthsRecalculation() mechanism to fix this,
instead of inventing something new.
This fixes most of the demo in bug 1037790, except when attempting to
reduce column-count to 1.
https://chromium-review.googlesource.com/c/chromium/src/+/1985770/1
will fix that.
Bug: 1037790
Change-Id: I9d42448f8cc7a5b170c98a59bcde7a916cea22db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985769
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728390}
--
wpt-commits: 52ad8a87fb72bcf6950c20cced0d87f34e26dc81
wpt-pr: 21010
Automatic update from web-platform-tests
Editorial: start using blocklist
As per https://whatwg.org/style-guide.
(Some tools/third_party/ is also guilty of this, but is likely harder to change.)
--
wpt-commits: 3e77495f7f1920daa0c706e7b287dee0ef3279e2
wpt-pr: 21024
Automatic update from web-platform-tests
[image-orientation] Move tests to WPT and add additional tests
Move all the web_tests for image-orientation to external/wpt.
Update the testing methods to wpt standards.
Adjust the test images to be ammenable to ref tests, though fuzzy matching
is still required.
Round out the test suite for <img> tags, content images and image documents.
Bug: 158753
Change-Id: Iff393f350cbecfc66a91811c72b0ee6274289e5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980505
Auto-Submit: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728358}
--
wpt-commits: 04d020981550e59c6cd9dc5376b8630998d878ec
wpt-pr: 21034
Automatic update from web-platform-tests
Change ChooseFileSystemEntriesType to be lowercase, dash-delimited
Per the spec [1], the ChooseFileSystemEntriesType should be lowercase,
dash-delimited, such as `save-file`.
[1]: https://wicg.github.io/native-file-system/#api-choosefilesystementries
Bug: 1020715
Change-Id: Iafc02db7344c70589cf007a7d66b9cd3f9dda6a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981515
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Cr-Commit-Position: refs/heads/master@{#728357}
--
wpt-commits: aa9924b906248e22f80da61a606ee8c473cadf38
wpt-pr: 20917
Automatic update from web-platform-tests
Add fake world test helper, misc other changes
Clean up and changes required to bring in WPT tests for hit test API.
- minor clean up in webxr-test.js - store input_sources_ in a map,
add 2 setter methods since the mojo properties were renamed but keep
the old setters for back-compat
- add webxr_test_constants_fake_world.js with logic to create a valid
FakeXRWorld with given dimensions and a constant VALID_FAKE_WORLD
- move transform-related asserts to webxr_test_asserts.js, change
all variables storing the assert functions to `const`, add semicolons
- add `DVLOG(3)`s in XRHitTestSource and XRSession
Changes:
Change-Id: I98ac5ed09cda877afb24e28df09ee4cd818d56f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986326
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728287}
--
wpt-commits: c5f090c0e768bccdc6b0c7711c4adc2d3311c230
wpt-pr: 21029
Automatic update from web-platform-tests
[LayoutInstability] Fix failures in tests shifting in/out of viewport
Currently, some tests work under the assumption that the height of the
viewport is exactly 600px. While this is true for tests running on our
bots, it's not true for tests running on WPT.fyi. Thus, this assumption
is removed from those tests.
Bug: 1036013
Change-Id: I34b057730e22bc208cbb958d179195445def8b77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1984678
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728280}
--
wpt-commits: 63f94078836eba226cdf0460b09482c8f9a6ae5d
wpt-pr: 21030
Automatic update from web-platform-tests
Fix test flakiness in reverse-running-animation
The animation was often finishing before the screenshot resulting in a
failure. Extended the duration of the animation and starting the
animation from the midpoint should address the flakiness without
needlessly extending the run time of the test.
Bug: 1029543
Change-Id: I32e7794ff77a3b26e7d7f260f80d4b00bbc9d6f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986212
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728253}
--
wpt-commits: b00f0cedac3a1e6dd42beb5884b303eac03e6c4b
wpt-pr: 21012
Automatic update from web-platform-tests
HTTP: 0x00 in a header value
Tests to complement those written in https://github.com/web-platform-tests/wpt/pull/10424.
--
wpt-commits: 38ecde806a5f1710d9e5beba700cef7352f7570e
wpt-pr: 21019
Automatic update from web-platform-tests
[css-pseudo] Move all ::marker style adjustments into StyleAdjuster
LayoutNGListItem was applying some style adjustments to markers, like
'white-space: pre' to preserve trailing spaces in outside markers.
But this was only affecting markers with 'content: normal', and the
changes weren't exposed in getComputedStyle().
This patch moves these adjustments into StyleAdjuster, so that all
markers are affected equally.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-018.html
The test fails in legacy because the 'content' property is not supported
yet in ::marker.
There is a new failure in marker-supported-properties.html because now
'white-space' will compute to 'pre' in outside markers, even if you
specify a different value. But normal markers were already enforcing
'pre' at used value time anyways.
Change-Id: I6d8b8ec7fb26cb04402032924f87b2c3b8fdb9cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985966
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#728176}
--
wpt-commits: a3111814fa0e9de6e2decd443d170a6e88304164
wpt-pr: 21011
Automatic update from web-platform-tests
html: Fix form constraints validator (#21014)
This commit applies two fixes to the validator:
1. Reapply the conditions for each clone of the element created in
iterate_over.
This fixes valueMissing.html's "[select] Selected the option with
value equals to 1" test, that was failing on all browsers.
2. Fix the expectation for validationMessage when the element is
disabled. This fixes#20825.
--
wpt-commits: bc5671c220564dd1fcc6c6a36dd20aaa0ba5e771
wpt-pr: 21014
Automatic update from web-platform-tests
[webnfc] NDEFMessageInit#records is required and should not be empty
NDEFMessageInit#records is the only field of the dictionary
NDEFMessageInit, it's required, and being empty makes no sense for
constructing an NDEFMessage object.
BUG=520391
Change-Id: I87fd3fae3bbbba449d9068c0992ded2080e435b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1983435
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#728120}
--
wpt-commits: 2dae72cf58b13994dbadf22353ed4aa35bafa587
wpt-pr: 20936
Automatic update from web-platform-tests
Portals: Use WebContents::ClosePage to run unload handlers for portals.
On the way, refactor how the Portal <-> WebContentsImpl pointers are
maintained, as this work caused the raw WebContentsImpl* to dangling while
writing the main code of this CL, which made for a confusing bug. This
refactoring is mainly a mechanical gathering of the code responsible for
updating these into a small nested class.
Bug: 964481
Change-Id: I8a63e1a5531de4807569b35ea0f3fcb19baf343c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1976000
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728057}
--
wpt-commits: 37a6910565388a7dc76aedd17c3aa74400d39286
wpt-pr: 20953
Automatic update from web-platform-tests
[css-pseudo] Let non-replaced images be list items with markers
<img> elements are usually replaced, so they can't originate a ::marker
pseudo-element even if they have 'display: list-item'.
However, if they point to an invalid image and have an alternative text,
then they are not replaced. Therefore they can have ::before and ::after
pseudo-elements, and also a ::marker if they have 'display: list-item'.
Before this patch, markers with 'content: normal' were never generated.
And non-normal ones worked fine in the inside case, but when outside
they triggerede a DCHECK failure because the marker was created but not
laid out.
BUG=1038644
TEST=external/wpt/css/css-pseudo/marker-content-017.html
The test fails in legacy because the 'content' property is not supported
yet in ::marker.
Change-Id: I4420bc2e9a0460f3a59fa030e5e3d249428aa6be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985759
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#728012}
--
wpt-commits: cb0d9cacbbf30a4cae79faa2e711c26456249b8c
wpt-pr: 20998
Automatic update from web-platform-tests
Add test that datachannels close when connection does. (#20787)
Bug: chromium:1030631
Change-Id: I322374725ef4a05b0c6d83fc2971061952441718
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969351
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725278}
Co-authored-by: Harald Alvestrand <hta+github@alvestrand.no>
--
wpt-commits: 99dac72cb20c21de36483f0e0b56d802075fe24f
wpt-pr: 20787
Automatic update from web-platform-tests
Don't detach old slotted nodes which have been adopted.
If the flat tree children of a a slot is not up to date during
DetachLayoutTree, they may contain nodes adopted into another document
since the previous reassignment.
Make sure we don't DetachLayoutTree for such nodes during when a flat
tree ancestor is RemovedFromFlatTree. This bug is a regression for
FlatTreeStyleRecalc since we used to traverse the tree for
DetachLayoutTree in light tree order.
This regressed with crrev.com/b225e2e72d4b083e635bf6abb3fc0daeb4ab4930
Bug: 1035228
Change-Id: Ibd4c03dee855851c120eebf1010a9b127827f7cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985839
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#728000}
--
wpt-commits: 8aacd823f26b4d5a66f6a8774381a058f8d151a6
wpt-pr: 20999
Automatic update from web-platform-tests
wpt: dont fire RTCPeerConnection.onconnectionstatechange on close
adds a test to assert that RTCPeerConnection.onconnectionstatechange
is not fired when RTCPeerConnection.close() is called.
BUG=699036,1023736
Change-Id: I623deeb4f0948cf213ff8913c33610ef0e7315e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1959969
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/master@{#727996}
--
wpt-commits: 4df69e91a0c5d7a8eb61fadb4bd5ffe7ee93f37f
wpt-pr: 20703
Automatic update from web-platform-tests
rtcpeerconnection: dont fire signalingstatechange from close()
RTCPeerConnection.close() shall not fire events. It doesn't already for
iceconnectionstate/connectionstate
BUG=699036
Change-Id: I771cdd81c3bbdb4312a623e96f8150be8471d906
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1959042
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727965}
--
wpt-commits: d858c038e3056c20d791089484e6b61a2fbc939d
wpt-pr: 20709
Automatic update from web-platform-tests
[css-pseudo] Fix WPT expectations for marker-font-variant-numeric-*
The marker-font-variant-numeric-default.html test is supposedly passing
in Chromium according to Chromium, but not according to wpt.fyi. The
reason is that in certain configurations, the test may look slightly
different than the reference due to font anti-aliasing.
The marker-font-variant-numeric-normal.html fails in all browsers due to
lack of support for nested ::marker selectors, but there are also some
differences in the parts that should actually match the reference.
This patch fixes both issues.
Bug: 457718
Change-Id: Id646b7810aed18441e1c7b37ad7bb1a37877be2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980174
Reviewed-by: Manuel Rego <rego@igalia.com>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#727963}
--
wpt-commits: 5449025de1490e2caf8eb67b2b017e78afa179b1
wpt-pr: 20907
Automatic update from web-platform-tests
Revert "Disable infra test that's causing CI failures" (#20952)
This reverts commit db7735a94c60d9b04d80035d76a723762de38c5c.
--
wpt-commits: 3486855609a5b0272996b3faa118b447e7fae1b1
wpt-pr: 20952
Automatic update from web-platform-tests
Add tests for type attribute values for rel=stylesheet links
This tests some edge cases. See https://github.com/whatwg/html/issues/5186 for follow-up.
--
wpt-commits: db1069b964c40cc9f0c072c0e925e8b15521dfd1
wpt-pr: 20930
Automatic update from web-platform-tests
wptrunner: Make sure payloads are encoded to binary before computing md5 hashes (#20918)
--
wpt-commits: c185f3d960eead15cd00f8c18409b8331bdb513e
wpt-pr: 20918
Automatic update from web-platform-tests
Replace call to cgi.escape by call to html.escape (#20919)
cgi.escape is deprecated since python>=3.2 and has been removed in
in python3.8
--
wpt-commits: a721e03f463f9fa8e768a7e41d568d97dc86041f
wpt-pr: 20919
Automatic update from web-platform-tests
Add test for error image with atrribute width and height (#20991)
The intrinsic size of error images shouldn't be overridden by the aspect-ratio from attributes width and height.
--
wpt-commits: 112ad5ca55d55f6da2ccc7468e6dcc91b4e5d223
wpt-pr: 20991
There are multiple places where bogus non-empty transition rules can be created
before this patch when EffectSet's cascade information isn't up-to-date. That
can happen as described in bug 1606176.
Anyhow, in this particular call site, this is only used to filter from
transition rules effects that are from running animations, to implement:
https://drafts.csswg.org/css-transitions/#application:
> Implementations must add this value to the cascade if and only if that
> property is not currently undergoing a CSS Animation ([CSS3-ANIMATIONS])
> on the same element.
In the test-case, the EffectSet cascade info is empty, so we hit the "skip
everything" for animations (wrong), and "skip nothing for transitions" (also
wrong). This creates a transition rule node which then we never remove
(understandably, as the element never had a transition!).
This fixes the observables of this test-case, by checking the cascade level
(so that we don't create transition rule nodes with declarations coming from
animations). This is strictly more correct than what we were doing.
If we hit the proposed assertion after this change, this code may still create
transition rules that incorrectly override animations, but will never mint one
out of the blue which we'd then fail to remove (which is the problem the
test-case is hitting).
Differential Revision: https://phabricator.services.mozilla.com/D58333
--HG--
extra : moz-landing-system : lando
Given that `test_composition` which requires the pref is defined in
css/support/interpolation-testcommon.js and setting prefs in
testing/profiles/web-platform/user.js seems to have a problem (bug 1604085),
so this place is the best place to set the pref for now.
And setting the pref reverts bug 1605866.
Differential Revision: https://phabricator.services.mozilla.com/D58722
--HG--
extra : moz-landing-system : lando
This cleans up and also allows us to keep the distinction between content: none
and content: normal, which allows us to fix the computed style we return from
getComputedStyle().
Do this last bit from the resolved value instead of StyleAdjuster, because
otherwise we need to tweak every initial struct for ::before / ::after.
Differential Revision: https://phabricator.services.mozilla.com/D58276
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Replace call to dict.iteritems by six.iteritems
--
wpt-commits: 878422d33b13cf46ec0d4f4201536426137ecc62
wpt-pr: 20920
Automatic update from web-platform-tests
Add content-aspect-ratio and update the description in canvas-aspect-ratio (#20943)
* Update the description in canvas-aspect-ratio. And add a test for content style image, make sure the width and height attributes won't infer its aspect-ratio.
--
wpt-commits: 453b3f32d5ee5a855780f9c43adc4c77996ab128
wpt-pr: 20943
Automatic update from web-platform-tests
html: Fix <input type=time> stepUp()-stops-at-border test (#20961)
Currently, this test is the only one failed by all three major browsers
in the file. Discovered by Kevin Raynel <kevinr@theodo.fr>.
--
wpt-commits: 53266c3b093c765918b37c7bd76b166d3b86d1f4
wpt-pr: 20961
Automatic update from web-platform-tests
XPath: Do not accept whitespace characters other than #x20, #x9, #xD, and #xA
Specification: https://www.w3.org/TR/1999/REC-xpath-19991116/#NT-ExprWhitespace
Bug: 1036767
Change-Id: I337ec70fefe8259d50bcf89a67b6e73c68fa585f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980251
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727844}
--
wpt-commits: e08790c4a97eb7d4ad8a13b1f917bfae3b08d334
wpt-pr: 20906
Automatic update from web-platform-tests
Disallow recursive custom element constructions
With this CL, recursive custom element constructions are no
longer allowed. I.e. this will now only run the constructor once:
class extends HTMLElement {
constructor() {
super();
customElements.upgrade(this);
}
}
Previously, the code and spec had a bug which caused the above
code snippet to infinitely recurse. In [1] the spec has changed,
to set the custom element state to "failed" before the constructor
is called. With this change in place, recursive calls will
early-out at step #2 (of [2]), and avoid the recursion.
[1] https://github.com/whatwg/html/pull/5126
[2] https://html.spec.whatwg.org/multipage/custom-elements.html#upgrades
Bug: 966472
Change-Id: I76e88c0b70132eee2482c304ef9e727ae1fe8fc7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931644
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727841}
--
wpt-commits: 4f24cabbe1f503f3daf8cf0834f4fb1a032f31bc
wpt-pr: 20465
Automatic update from web-platform-tests
[web-animations] Fix test in setting-the-playbackrate-of-an-animation.html (#20905)
This test assumes that currentTime will not change after waiting for
ready but the spec does not require that so this patch inverts these two
lines.
--
wpt-commits: c328e2ae1924a40d07dc552c4587ecc649eef0fd
wpt-pr: 20905
Automatic update from web-platform-tests
[LayoutInstability] Fix flaky tests
In this CL, some 'await waitForAnimationFrames(2)' are added to wait for
the initial render of the test page before introducing the observer.
This removes flakiness of these tests in WPT.fyi. Other cleanups are
done in the test files.
Bug: 1036013
Change-Id: Ic2631faf03ad00c8e32013c100c3b4ab867be2b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982708
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727639}
--
wpt-commits: 11f1a592c17fb4a7bb5c3081493ebb6a04a0aa39
wpt-pr: 20924
Automatic update from web-platform-tests
[LayoutInstability] Cleanup test observe-layout-shift.html
Currently, the test contains two async_tests, which is not good because
they run in parallel so the tests can affect each other. The first test
is redundant with buffer-layout-shift.html. The second test uses a
helper function from EventTiming, so we import the script instead of
copy-paste and we rename the test.
Change-Id: Ibe6d200441a07c603bccf0858406cf2c4f1d37a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982710
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727640}
--
wpt-commits: a3f46a8e90c9bf8e0c860525cce7ae5f10654234
wpt-pr: 20926
Automatic update from web-platform-tests
[webnfc] Correct error type
Per spec:
If languageLength cannot be stored in 6 bit (languageLength > 63),
throw a SyntaxError.
But current implementation throws a TypeError, this CL fixs the error type.
Bug: 520391
Change-Id: I6ff64d87b387a07fff926ada80e5ee5d73b716b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981199
Commit-Queue: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#727414}
--
wpt-commits: 36507c8b6fe2d51971da07c913589ef1621f1651
wpt-pr: 20915
Automatic update from web-platform-tests
LazyLoad: Timeout when moving image elements between documents
This CL adds WPT test for moving image elements between documents
as well as removing image elements.
Bug: 1001968
Change-Id: I725b60bfaf2406d7fdeabe8d4422d0618dc29478
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967084
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#727350}
--
wpt-commits: 7ed322c3132993bcb5734702b40621448670fc76
wpt-pr: 20774
Automatic update from web-platform-tests
Add support for running crashtest tests with webkitgtk (#20914)
* This adds support in the webkitgtk_minibrowser, webkit and epiphany
product runners for running crashtest tests.
--
wpt-commits: e936890351047304cdc98d31d555f6d6a068097e
wpt-pr: 20914
Automatic update from web-platform-tests
[Native File System] Writable File Stream
This implements a WritableStream-based API.
WritableStream methods are fully implemented.
Operations are queued and the WritableFileStream can be piped to.
tell() queuing tracked at https://crbug.com/1034210
Transferability tracked at https://crbug.com/1035673
More information in the design doc: https://bit.ly/36wfLFA
BUG=955189
Change-Id: Ibd2e0a29c230a2fa25b6133fdbaac4f4ad4f1eb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913586
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727179}
--
wpt-commits: da7be43c647270534d83c44d6af9a76ca1faf1d1
wpt-pr: 20261
Automatic update from web-platform-tests
Use HTTP_NOTSAMESITE_ORIGIN for split cache Web Platform Test
Currently HTTP_REMOTE_ORIGIN is used as the third-party origin, but
this does not work for split cache experiments using eTLD+1 as the
additional key (i.e. when UseRegistrableDomainInNetworkIsolationKey is
enabled). This is due to HTTP_REMOTE_ORIGIN simply prepending 'ww1.' to
the HTTP_ORIGIN, which results in the same registrable domain.
Bug: 1035508
Change-Id: Ib42bb30491bb451a47b80914a48e252a9c93d10f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978037
Reviewed-by: Shivani Sharma <shivanisha@chromium.org>
Commit-Queue: Alex Turner <alexmt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727110}
--
wpt-commits: 44e3f8a64aacebd5123aac7456cb81f423c38860
wpt-pr: 20880
Automatic update from web-platform-tests
[IndexedDB] Adding web platform test for index tombstones
This web platform test ensures that indexes update correctly for
cursors. If an implementation creates tombstones for index updates, then
this should test that those tombstones are ignored.
R=jsbell@chomium.org, pwnall@chromium.org
Bug: 1033996
Change-Id: I07585d9ec065b1ad4f8b720efceaca0987984869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972579
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726918}
--
wpt-commits: 560d73983d08fd0e36244f743d8c54a3b18e558c
wpt-pr: 20821
Automatic update from web-platform-tests
Enable file uploads in web_tests via testdriver-vendor.js.
testdriver supports file uploads via send_keys to the input element,
on the other hand eventSender supports file uploads via drag&drop to
the input element. So this CL implements test_driver_internal.send_keys
by using the drag&drop functionality if the target element is an
<input type=file>.
Also fixes a bug in file_upload.sub.html where backslashes in the file
path weren't being escaped, resulting in the test not working on windows.
Change-Id: I9a446f8dac3ae7817bb03ba9592d2537223b0f33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974849
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726873}
--
wpt-commits: c8158bdeea965ceecd5a95d507e75e863fdc6d0e
wpt-pr: 20857
Automatic update from web-platform-tests
Change how wptrunner computes reftests (#20459)
This preserves the current data structures within wptrunner as it
passes them onwards to Marionette currently in the Firefox case, and
as such changing them involves changes within Firefox too.
Those changes within Firefox are ones we should make, and is tracked
by https://bugzilla.mozilla.org/show_bug.cgi?id=1598340, before
changing how reftests are represented within wptrunner.
--
wpt-commits: e9fe7bf0c8d0d48f4fc36d6631c1d05af071792c
wpt-pr: 20459
--HG--
rename : testing/web-platform/tests/infrastructure/metadata/infrastructure/reftest/reftest_fuzzy_chain_ini.html.ini => testing/web-platform/tests/infrastructure/metadata/infrastructure/reftest/legacy/reftest_fuzzy_chain_ini.html.ini
rename : testing/web-platform/tests/infrastructure/reftest/fuzzy-ref-2.html => testing/web-platform/tests/infrastructure/reftest/legacy/fuzzy-ref-2.html
rename : testing/web-platform/tests/infrastructure/reftest/fuzzy-ref-2a.html => testing/web-platform/tests/infrastructure/reftest/legacy/fuzzy-ref-2a.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_fail.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_fail.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch_0.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch_0.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch_1.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch_1.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_0-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_0-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_1-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_1-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_fail.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_fail.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_fail_0-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_fail_0-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_fuzzy_chain_ini.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_fuzzy_chain_ini.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_or_0.html => testing/web-platform/tests/infrastructure/reftest/reftest_multiple_match-0.html
Automatic update from web-platform-tests
Add a way to signal AR support through FakeXRDeviceInit
Aligns our MockRuntime implementation to changes introduced by:
https://github.com/immersive-web/webxr-test-api/pull/45
Change-Id: Icd33b566118501457c338a1d7882d260bf3f48e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974310
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726856}
--
wpt-commits: cfa8792159ff63e208d4133ce692d2980bb41f90
wpt-pr: 20847
Automatic update from web-platform-tests
[css-pseudo] Properly set 'display: inline-block' to outside ::marker
Before this patch, outside markers were assigned 'display: inline-block'
but this happened in two different places: in LayoutNGListItem for
markers with 'content: normal', and in StyleAdjuster for content ones.
However, this meant that 'getComputedStyle(el, "::marker").display'
would be 'inline' in the former case and 'inline-block' in the latter.
This patch fixes that issue by ensuring that StyleAdjuster runs for all
markers, assigning 'display: inline-block' to outside ones even when
'content: normal'.
This has a noticeable effect even if the CSSMarkerPseudoElement flag is
disabled: text decorations are no longer propagated to outside markers.
This is actually expected, since decorations shouldn't be propagated to
inline-block descendants. They were being propagated for markers with
'content: normal' because the code that stops the propagation either
wasn't running for unstyled markers, or for styled normal markers it was
running before 'display: inline-block' was assigned.
This change won't be a compat problem since none of Chromium legacy,
Firefox and Edge propagate text decorations to outside markers by
default. Doing it seemed a LayoutNG bug.
Spec: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo
Spec: https://drafts.csswg.org/css-lists/#list-style-position
Spec: https://drafts.csswg.org/css-text-decor-4/#line-decoration
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-016.html
TEST=external/wpt/css/css-pseudo/marker-display-computed.html
The marker-content-016 test fails in legacy since the 'content' property
is not supported yet in ::marker
Change-Id: Ia1396a4f6c5d9825dba5a6265c32096a7066fbed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975887
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#726783}
--
wpt-commits: 2cb652e543d379bafcb3d0d26e2de28836f22df4
wpt-pr: 20864
Automatic update from web-platform-tests
[EventTiming] Fix crossiframe test
This CL does the following fixes to crossiframe.html test:
* Remove slow-image and onload, which are obsolete assumptions.
Instead, rely solely on PerformanceObserver.
* Use awaits where needed to make the test logic more sequential.
* Use coordinates and test_driver.Actions() to target the iframe. Using
the test_driver.click directly won't work for elements in iframes.
* Updates the test to check reasonable values for the frame and iframe
entries and check that they don't receive each other's entries.
This CL also:
* Removes unneeded variables from the clickAndBlockMain().
* Removes manual test, which is no longer needed.
Bug: 831729
Change-Id: Iff50035a216b21f67cd71796023af4f934573086
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972249
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726422}
--
wpt-commits: 80e94e6d5113f3670e0b36c0a1fd905a43ce65d5
wpt-pr: 20819
Automatic update from web-platform-tests
Refactor data-feeding for ImageDocument/ImageDocumentParser
ImageDocumentParser keeps the ImageResource for ImageDocument and passes
the associated ImageResourceContent to the HTMLImageElement used for the
ImageDocument.
This eliminates ImageDocument::CachedImageResourceDeprecated and cleans
up ImageDocument<->ImageDocumentParser interaction a bit.
The creation of the ImageResource now takes place in the first call to
ImageDocumentParser::AppendBytes rather than indirectly via a call to
ImageDocument::CachedImage.
Set ImageLoader::image_complete_ in the same as for regular image-loads,
and start dispatching 'load' (and 'error') events for the <img> element
in the image document. This behavior matches Gecko.
Bug: 958339
Change-Id: Iacdab89f6894adf70163f0d5300aefc9b2fce4e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975921
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726803}
--
wpt-commits: 25ec2153abd47ea8b7a8cba23b3f153167c0805d
wpt-pr: 20889
Automatic update from web-platform-tests
[css-layout-api] IntrinsicSizes Implementation
This change adds support for the CSS Layout API intrinsicSizes()
callback function. The implementation closely matches that of the
layout() callback function.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#intrinsicsizes
- Algorithm:
https://drafts.css-houdini.org/css-layout-api/#invoke-an-intrinsic-sizes-callback
The implementation also involved exposure of the
IntrinsicSizesResultOptions type.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#dictdef-intrinsicsizesresultoptions
Support was also added for the Child intrinsicSizes() function.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes
- Algorithm:
https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes
Bug: 726125
Change-Id: Ifc6064e069b4c9c5218c9d783b7d9de6a480e7ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949536
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725834}
--
Rename some colliding references
--
wpt-commits: f160db31bb6fdf94c6c914a779a1b47b9e0e4e30, 5f8d15ebdcf0495c271c81776971061be1366445
wpt-pr: 20682
--HG--
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/absolute-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-absolute-ref.html
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/floats-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-floats-ref.html
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/negative-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-negative-ref.html
rename : testing/web-platform/tests/css/css-layout-api/fallback-layout/fallback-ref.html => testing/web-platform/tests/css/css-layout-api/fallback-layout/fallback-layout-fallback-ref.html
Automatic update from web-platform-tests
COEP: Enforce CORP in cache.match()
Document using:
"Cross-Origin-Embedder-Policy: require-corp"
must not access cross-origin response that do not have the header:
"Cross-Origin-Resource-Policy: cross-site"
This is about only no-cors requests. CORS requests are checked against the
CORS headers instead.
See:
- https://github.com/whatwg/fetch/issues/985
- https://github.com/w3c/ServiceWorker/issues/1490
Bug: 1031542
Change-Id: I94a2cb9435fcf3e76f57a8f3d3344c87fa23f9a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973913
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726782}
--
wpt-commits: 236e6dbc70e128ab5ff5bad6ab98888281df8ffd
wpt-pr: 20840
Bug 1594748 enabled cross origin opener policies but only on desktio Nightly.
Differential Revision: https://phabricator.services.mozilla.com/D58565
--HG--
extra : moz-landing-system : lando
This is the right thing to do, and prevents a race where we try to log
after the stdout capture queue is closed
Differential Revision: https://phabricator.services.mozilla.com/D56567
--HG--
extra : moz-landing-system : lando
This commit changes IsBidiLeaf to mark ruby boxes not a bidi leaf, since
conceptually they are not. I auditted all uses of it, and I believe it
makes more sense this way.
Differential Revision: https://phabricator.services.mozilla.com/D58290
--HG--
extra : moz-landing-system : lando
Do the same we do for classes for now. We could be more precise and achieve a
bit more sharing with some more effort (left a comment there), but it seems
unlikely to matter in practice (and if we did that, we'd probably want to do the
same for classes).
Differential Revision: https://phabricator.services.mozilla.com/D58453
--HG--
extra : moz-landing-system : lando
This matches other browsers.
Keep the restriction just to chrome nodes, and in that case, avoid getting into
the broken state, which is what causes the issue. I'm not sure if this even
matters anymore given e10s but...
Differential Revision: https://phabricator.services.mozilla.com/D57475
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Service worker: updating ready tests (#20655)
* Modernising ready test
* Removing test that no longer applies
* Waiting for activate
--
wpt-commits: 8986297ff16650c6cad632fcacfba7c2f9054ea7
wpt-pr: 20655
Automatic update from web-platform-tests
[css-grid] Grid align content distribution tests (#20110)
* add content distribution test, including cases for vertical-lr and vertical-rl
--
wpt-commits: efb47196a63bdb8c0cfdcc9415ab58bbbf02e0c0
wpt-pr: 20110
Automatic update from web-platform-tests
[webnfc] Reject the push when a non-NDEF tag comes in proximity
Previously, when a non-NDEF tag comes in proximity, NDEFWriter#push()
does nothing and still keeps in pending state.
This CL switches to reject NDEFWriter#push() in such case so that WebDev
can get a sense of what's happening.
BUG=520391
Change-Id: I17569910466e75f12ff4e37c29180e2a9af9db13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967745
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#726643}
--
wpt-commits: 256b4685b8e702c14ed854347f23f4979edbfc8e
wpt-pr: 20859
Automatic update from web-platform-tests
CSP: Parse and report violations from Content-Security-Policy-Report-Only
headers in the browser process.
Bug: 759184
Change-Id: Iefb33fa8ec2264f3e224d5a3ab92417160848fdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958692
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726618}
--
wpt-commits: be373901c6e71b8a14e9e2235a4961ef2ab62bfb
wpt-pr: 20688
Automatic update from web-platform-tests
XPath: Fix normalize-space()
It should handle only XML white spaces; #x20, #x9, #xD, and #xA.
We incorrectly handled other white spaces such as U+3000.
Bug: 893929
Change-Id: I59708f978ba1c23141f748de7a8f4c58d58c7acf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974713
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726557}
--
wpt-commits: 3a9bcdca3cf0ce754528e5c2e5503bb07ea3af9d
wpt-pr: 20861
Automatic update from web-platform-tests
Never let a non-zero-size pixel snap to zero size
The logic for LayoutUnit::SnapSizeToPixel maps the size to
the closest pixel align edge given a location. When a size of
width less than 1 happens to straddle a pixel aligned edge this
forces the size to zero.
Force the size to always be non-zero if the input size is non-zero,
and change PhysicalRect to use the LayoutRect snapping to get
correct cull rects.
Bug: 793785
Change-Id: Ia4c30d10c389fb4677006441aac9ee380a7c2f41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948057
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726516}
--
wpt-commits: 30896bb9378b84ffd5583a1088d4e2862f19dc66
wpt-pr: 20871
Automatic update from web-platform-tests
Implement new pseudoElement interface on KeyframeEffect
Make target() return the originating element if target_ is a
PseudoElement (EventTarget still returns the layout object).
Add pseudoElement() property which returns the target pseudo-selector
if the target is a pseudo-element (null otherwise).
Invalid and unsupported pseudo-elements will still return a selector
and the originating element (from target()) but will not animated
(EventTarget returns null).
Add pseudoElement option to KeyframeEffect constructor.
Change-Id: Id7d16ea6966c533e56d1170462ff60a79b277fd5
Bug: 981894
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1921343
Commit-Queue: George Steel <gtsteel@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726506}
--
wpt-commits: 084d8726a0cde51d0fdd1e4bc375fa8788b6835b
wpt-pr: 20373
Automatic update from web-platform-tests
Fix `text-overflow: ellipsis` when `text-indent` is also applied
This patch fixes `text-overflow: ellipsis` to take the space
occupied by `text-indent` into the account.
Bug: 1006395
Change-Id: I417176efbc8f10fa3c073efa7695458fb2d302a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975372
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726504}
--
wpt-commits: 50046d4a51fe25bb4afc4883579a4b067e3137e0
wpt-pr: 20858
Automatic update from web-platform-tests
Origin policy: update feature policy parsing to match the latest spec
This updates the parsing of the feature policy parts of the origin
policy manifest to mostly match the latest spec draft at
https://wicg.github.io/origin-policy/, in particular
https://wicg.github.io/origin-policy/#parsing. That is, it moves away
from "feature-policy": ["... FP string"] to
"features": { "policy": "... FP string" }. This changes the data model
from a list of FP strings to an optional FP string. Additionally, it
removes the failure on parsing errors, as those are no longer in the
spec.
This does not yet properly parse the FP string as a FP directive;
instead it still treats it as a header (so, commas are allowed inside).
A failing test is added for that case, which will be addressed in a
followup CL.
Bug: 751996
Change-Id: I51711ee9381ecfc705683ba0eb870e461fed434e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965905
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726494}
--
wpt-commits: db14bfd40ccbf3cd633d759c96329b36ff1b53b6
wpt-pr: 20772
Automatic update from web-platform-tests
[css-pseudo] Recalculate viewport units in ::marker (#20795)
If a marker uses viewport units (vw or vh), they should be recalculated
when the size of the viewport changes.
This patch updates node traversal methods to include ::marker, so that
it's taken into account when updating viewport units.
However, this is only fixed for markers with non-normal content, since
otherwise they aren't implemented as real pseudo-elements yet.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-014.html
The test still fails because it includes cases with 'content: normal'.
Change-Id: I7495dd5c4bbd84d6286635a63199bfcc663c62c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970015
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#725463}
--
wpt-commits: 6d7a762c4c65d06fc95752f17ce96426c7b2d441
wpt-pr: 20795
Automatic update from web-platform-tests
[scroll-to-text-fragment] Apply :target CSS pseudo-class to match.
Per the spec, the common ancestor element of the match range becomes the
target element[1] and should have the :target pseudo-class applied.
[1]
https://html.spec.whatwg.org/multipage/browsing-the-web.html#target-element
Bug: 959163
Change-Id: Idb462a17972f4758df9617653f03b88196fd565a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965273
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726031}
--
wpt-commits: 7139b3d0aaeebe6cd40e62c46c06df630a49c2dd
wpt-pr: 20753
Automatic update from web-platform-tests
[OT-PW] Make it work with OOP-R
This CL makes off-thread paint worklet work with OOP-R. OOP-R serialize
an PaintOp and stores the serialized buffer in a shared memory. GPU
then reads the memory and de-serialize it.
For off-thread paint worklet, we are producing a DrawImageRectOp. Note
that this DrawImageRectOp is different than a normal one. It is a
DrawImageRectOp that contains a DrawRecord that contains multiple
PaintOps in it. So this CL adds a special code path to serialize it,
for paint worklet DrawImageRectOp only. The way to serialize it is to
iterate over all the PaintOps inside the DrawRecord. In this way, we
do not need to change anything on the GPU de-serialize code.
We also changed the layout tests. We changed some tests, now using
fillRect instead of strokeRect.
The problem with strokeRect is that using GPU rasterization could
easily result in subpixel difference on different platforms. Using
fillRect will avoid that.
Bug: 1020238
Change-Id: Ie0aadfe217e462547cc16a273d09ec8a64f055a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1957012
Reviewed-by: Yi Gu <yigu@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725554}
--
wpt-commits: 15e4f2b5a97b2fcd14c592f2de16cc62a82c645d
wpt-pr: 20705
Automatic update from web-platform-tests
Use Image::SizeAsFloat() and unsnapped rectangle in ImagePainter
The pixel-snapping of the destination rectangle can end up distorting
the geometry use for painting an SVG image preserveAspectRatio is used -
the larger the aspect ratio, the larger the error.
By passing the unsnapped rectangle to LayoutImageResource::GetImage, and
using Image::SizeAsFloat() to compute the source rectangle of the image,
e can minimize the error and allow the Image in question (an SVGImage)
to perform compensation for the difference in aspect ratio between the
snapped and unsnapped rectangles. This means that the painted result
will better approximate the intended rendering.
Also clean up accesses to the LayoutImageResource and ImageResourceContent
by adding and using local variables for them.
Bug: 812239
Change-Id: I0778648e7dd6fcca778a95123509f15b3519564c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969831
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#726375}
--
wpt-commits: 8e4a2c71523b8b9c078a6500711ff7ec1aa69bf4
wpt-pr: 20831
Automatic update from web-platform-tests
Fix OffscreenCanvas.convertToBlob worker exception tests
Previously they would always pass, regardless of the result.
--
Add SecurityError tests to offscreen-canvas/convert-to-blob
--
wpt-commits: df1173b63aa2e982309b50b4863256dce0c6436e, ff028c837c33dd07e62f927ce37844963e132369
wpt-pr: 20695
Automatic update from web-platform-tests
Add a test for serializing Module for storage.
--
wpt-commits: 0ae74ec621f758cfe426ab7cb71b5dd6be0a241c
wpt-pr: 20554
Automatic update from web-platform-tests
[css-pseudo] Let 'content' ::markers be forced to be inside
Even if a list item has 'list-style-position: outside', Chromium may
force its marker to be inside when it's a <li> outside a list element.
This information was stored in layout, but this created an undesirable
dependency since the computed 'display' value of the marker depends on
whether it's inside or outside. And it wasn't possible to force a marker
with non-normal 'content' to be inside.
This patch fixes it by adding an internal 'IsInsideListElement' flag in
ComputedStyle. This design also avoids traversing all the ancestors of
every <li> element.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-015.html
The test fails in legacy since 'content' is not supported yet.
Change-Id: I2df70841e8e9d729fd4aa47ec9b9973c09a82dcb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973914
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#726310}
--
wpt-commits: f61f56f084c397f6d46ffd18723300a124d12ea5
wpt-pr: 20837
Automatic update from web-platform-tests
[webnfc] Dispatch error events when failed to read a nfc tag
Trigger NDEFReader#onerror on all active readers when we found that the
nfc tag coming nearby is not NDEF compatible or some IO errors happened
when trying to read the tag, etc.
BUG=520391
Change-Id: I1cb0de0474942c9912cba465cb9d14c035e948c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1960479
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#726253}
--
wpt-commits: 1268bd5901289acc95b1a576f108bdf382d82e44
wpt-pr: 20739
Automatic update from web-platform-tests
Disallow serializing and transferring non-origin-clean ImageBitmap (#20526)
The tests update for https://github.com/whatwg/html/pull/5114.
Add one test case for serialization, add one test case for
transferring. The relationship between COOP/COEP is now clear
and we can remove no-coop-coep.https.window.js.
--
wpt-commits: 578b1c621b57c2ad51442cb273bd5b8ea1dfed63
wpt-pr: 20526
Automatic update from web-platform-tests
XPath: Fix context node of rhs of union operator
The new behavior matches to Edge and Firefox.
Bug: 908632
Change-Id: I0dbb861e93836284a0c474cc486650dab27dc7b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973333
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726224}
--
wpt-commits: 3b8c7cec5f46c01850da7614058dae83ef2246c3
wpt-pr: 20828
Automatic update from web-platform-tests
XPath: Fix context node after evaluating an expression in a predicate
The new behavior matches to Edge and Firefox.
Bug: 625710
Change-Id: I27de8b769712062f548eb9d2274544d1ec0ff073
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973435
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726221}
--
wpt-commits: 1f3cbfb43e511f4707d8ec832089cae804546860
wpt-pr: 20829
Automatic update from web-platform-tests
Use [RaisesException] for immediate promise rejections in bluetooth
This is a part of effort for using [RaisesException] when synchronously
rejecting a promise.
It uses [RaisesException] for
//third_party/blink/renderer/modules/bluetooth.
Bug: 1001114
Change-Id: Iddb31cbbf71637ae989ea634f78207dfd9289c43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971049
Commit-Queue: Julie Kim(OoO til Jan 01) <jkim@igalia.com>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726215}
--
wpt-commits: 8934608dc507921b3701463053282909c5a86984
wpt-pr: 20808
Automatic update from web-platform-tests
Use XRSessionMode where appropriate
Refactor XRSessionOptions and XRRuntimeOptions to use an enum,
XRSessionMode, where appropriate rather than a pair of bools.
As the WebXr spec evolved, the mojom definitions evolved with it. Now
that WebVr has been removed and the spec has been solidified, this
refactors portions of the mojom to fit better and simplify the code. As
a result, a blink-side enum was able to be replaced with this new mojom
enum. Unfortunately, a device-side enum was not able to be removed, but
it was able to be scoped to just the SessionMetricsHelper. Hopefully
future cleanup will enable removal of this enum as well.
A couple of changes are worth calling out specifically:
Some slight behavior changes were added, which fit with the expectations
of the code. Namely, some runtimes that only checked for "immersive",
and not "environment_integration", now assert that the request is for
"ImmersiveVr", which more closely reflects reality.
XrRuntimeManager::GetRuntimeForOptions was also cleaned up from a more
complicated set of if-blocks to a switch statement.
Fixed: 1035205
Change-Id: I09f39d4a80f1454d5a9aa58fb785169ba5338510
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973156
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726205}
--
wpt-commits: b2e541f880ab1d03f0ba58b80a05993c43e2a8fc
wpt-pr: 20848
Automatic update from web-platform-tests
webxr-test: reset input source's clicked state after use
Using 'simulateSelect()' should generate only one "select" event, but since the
state value wasn't being reset it was also creating additional ones for each
following frame. This wasn't causing problems for the single existing test
using it (events_session_select_subframe), but is a trap for other uses.
Change-Id: I87cd55b1c0654d0183aa39af9bd5ad178d7409da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974682
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726171}
--
wpt-commits: 269e7c07aa335a2d36279b2229b351fefbf98a80
wpt-pr: 20856
Automatic update from web-platform-tests
Preserve visual rect during layout tree reattachment.
Without this, a shift could hide from LayoutShiftTracker if the layout
tree had to be rebuilt due to a change in an ancestor's 'display'
property.
Bug: 1003459
Change-Id: Ib00772ff7846251533080b29d16f6cbaafc8189b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958191
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726137}
--
wpt-commits: 907bbfc36ceed7ad320e5175f329b70be318a854
wpt-pr: 20815
Automatic update from web-platform-tests
[CSS4Pseudo] Added 2 tests and 1 reference on selection and text-shadow
--
wpt-commits: b5b7813e9ce247495b0df30b2f9c8a35de2eacba
wpt-pr: 20802
Automatic update from web-platform-tests
Corrected a typo in float-shrink-to-fit-vrl-vlr-016.xht test
--
wpt-commits: 1799625e205a4457d879b6b9a3f74365f3b9cfd3
wpt-pr: 18602
Automatic update from web-platform-tests
Make interpolation-testcommon.js support composition
Port font-variation-settings-composition
Add composition test ability to external/wpt.
The Chrome passes all tests.
Firefox has a bug which give the output in reverse order.
Bug: 1034538
Change-Id: Ib71fc2518008144f7002eee95bff57fe90e05cce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965910
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725575}
--
wpt-commits: b4f67181463668e61186828d11abee6d079d98c3
wpt-pr: 20790
Automatic update from web-platform-tests
Make conditional tests of wptrunner/wptmanifest compatible with Python3
--
Make serialiazer tests of wptrunner/wptmanifest compatible with Python3
--
Make static tests of wptrunner/wptmanifest compatible with Python3
--
Remove Python3 warning in parser tests of wptrunner/wptmanifest
--
wpt-commits: 2c1056bc94b7f2b420b8c586c0a601179bb1c1e9, 0aeb5c3a498847759234d4f0cee0684dca1bdfd3, 9c60cbbec1bb47083a06532fc0de28ae18c71edd, 08f3e37808d3b46e1697fe365c3fb3206cbf8320
wpt-pr: 20801
Automatic update from web-platform-tests
Tick animation timelines individually.
Refactoring DocumentAnimations, AnimationTimeline, DocumentTimeline and
ScrollTimeline classed to support ticking timelines individually. This is
needed to support scroll timeline specific functionality, such as timing update
on scroll change and timeRange: 'auto'.
Changes made:
- Moved timeline common functionality to AnimationTimeline.
- Instantiate DocumentAnimations per document and have it manage all document
timelines.
- Attach animation to the timeline it was instantiated with instead of the
document's global document timeline.
Bug: 1030797
Change-Id: Ic4b61ac5ea0e7dbe0369b6b3ba81838208aa7d0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940301
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#726067}
--
wpt-commits: bf21d03497737638921b0947966867be30a8aac7
wpt-pr: 20621
Automatic update from web-platform-tests
Disable infra test that's causing CI failures
--
wpt-commits: db7735a94c60d9b04d80035d76a723762de38c5c
wpt-pr: 20839
moz-wptsync-bot
Yan, Shaobo
Markus Handell
autofoolip
Domenic Denicola
Mike West
Yifan Luo
Oriol Brufau
Chris Lord
Timothy Gu
Robert Liao
Wanming Lin
nordzilla
Joey Arhar
Xianzhu Wang
Anne van Kesteren
Nicolás Peña Moreno
James Graham
Marco Castelluccio
Dzmitry Malyshau
Jeff Walden
Dan Minor
Henrik Skupin
Tsuyoshi Horo
guest271314
Koji Ishii
teapotd
Morten Stenshorne
Stephen Chenney
Zhuoyu Qian
Piotr Bialecki
Kevin Ellis
Leon Han
Jeremy Roman
Harald Alvestrand
Blink WPT Bot
Rune Lillesveen
Philipp Hancke
Stephen McGruer
Rob Buis
Élie ROUDNINSKI
cathiechen
Edgar Chen
Ehsan Akhgari
Emilio Cobos Álvarez
Jonathan Kew
Narcis Beleuzu
Boris Zbarsky
Byron Campen [:bwc]
Cosmin Sabou
Hiroyuki Ikezoe
Kent Tamura
Mason Freed
haozhe
Brian Birtles
L. David Baron
Carlos Alberto Lopez Perez
Olivier Yiptong
pyup.io bot
Ms2ger
Alex Turner
Gérard Talbot
Daniel Murphy
Marijn Kruisselbrink
Sam Sneddon
Kai Ninomiya
Fredrik Söderquist
Alison Maher
arthursonzogni
Philip Jägenstedt
Tom Tung
Xidorn Quan
Ting-Yu Lin
Edwin Takahashi
Andreea Pavel
Perry Jiang
Jake Archibald
_Ros_
Lucas Gadani
George Steel
Domenic Denicola
Nick Burris
Xida Chen
Dominic Farolino
Yutaka Hirano
Julie Jeongeun Kim
Alex Cooper
Klaus Weidner
Steve Kobes
Olga Gerchikov