Automatic update from web-platform-tests
Add test for :nth-of-type selector with mixed namespaces
Elements with the same tag name but different namespaces should be
considered separate for :*-of-type selectors
Bug: 1405427
Change-Id: I13aff216919ebffdd20cd17b557be3578d6a3bcf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4141240
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1090245}
--
wpt-commits: 5579e434f988a9ad4c87a95d1943a906bb0f3c3e
wpt-pr: 37774
Automatic update from web-platform-tests
[ComputePressure] Fix flaky compute_pressure_duplicate_updates.tentative.https.window.html test
The test is flaky now, because we need to wait for multiple
PressureRecords and the time interval between PressureRecords
is one second which leads to timeout easily. This CL resolves the
problem by decreasing the time interval between PressureRecords.
Bug: 1376986
Change-Id: I844da7c0f6fc8cbe061557022444409b180a2ba1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4137236
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Reviewed-by: Fr <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/main@{#1090177}
--
wpt-commits: 876a45ef49a2e50b53875441112371a98301c274
wpt-pr: 37768
Automatic update from web-platform-tests
Extract customized builtin test cases out of custom-elements/Document-createElementNS.html (#37788)
Split custom-elements/Document-createElementNS.html into two files one testing autonomous
and another testing customized builtins for better tracking.
--
wpt-commits: 1a4a70f9a0a83be589eb2fa3a764e4304338decf
wpt-pr: 37788
Automatic update from web-platform-tests
Move customized builtin reaction tests to a subdirectory (#37794)
Move all the reaction tests for customized builtin to custom-elements/reactions/customized-builtins for clarity.
--
wpt-commits: 421155a1c8752a36b465e62f466b18f821190e08
wpt-pr: 37794
Automatic update from web-platform-tests
Rename custom-elements/parser/serializing-html-fragments.html for clarity (#37793)
Rename custom-elements/parser/serializing-html-fragments.html to custom-elements/parser/serializing-html-fragments-customized-builtins.html for clarity.
--
wpt-commits: cc02ae31b7f6c26b4996060759882b8bc38db7d3
wpt-pr: 37793
Automatic update from web-platform-tests
Extract customized builtin test cases out of custom-elements/upgrading/Node-cloneNode.html (#37792)
Split custom-elements/upgrading/Node-cloneNode.html into two files one testing autonomous and another testing customized builtins for better tracking.
--
wpt-commits: e697964552f7678c0714e35fe02b6b3ca7df3a9d
wpt-pr: 37792
Automatic update from web-platform-tests
Extract customized builtin test cases out of custom-elements/htmlconstructor/newtarget.html (#37791)
Split custom-elements/htmlconstructor/newtarget.html into two files one testing autonomous and another testing customized builtins for better tracking.
--
wpt-commits: ff8dc2b2bbc71af97f6e29c3ef8ea6697f512d1b
wpt-pr: 37791
Automatic update from web-platform-tests
Extract customized builtin test cases out of custom-elements/upgrading/Document-importNode.html (#37790)
Split custom-elements/upgrading/Document-importNode.html into two files one testing autonomous and another testing customized builtins for better tracking.
--
wpt-commits: e74fdee5eebcbffb34b234a0251e47d8b14c3639
wpt-pr: 37790
Automatic update from web-platform-tests
Extract customized builtin test cases out of custom-elements/pseudo-class-defined.html (#37789)
Split custom-elements/pseudo-class-defined.html into two files one testing autonomous and another testing customized builtins for better tracking.
--
wpt-commits: 3b1f7330a2570ddc37a2a7f3b1464252c311379f
wpt-pr: 37789
Automatic update from web-platform-tests
Rewrite larger-text.html and re-enable it
The test fails because, when the beforeRender timestamp is taken, the
text element which is the LCP element, may already be rendered as a html
element.
This CL fixes that by addings text and load images using JS after the
beforeRender timestamp is taken. This way, rendering is guaranteed to
happen after the beforeRender timestampt.
Bug: 1404826
Change-Id: Id12c196f4f4d498388c8e18bf0a8c072e3982314
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4134032
Commit-Queue: Hao Liu <haoliuk@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1089830}
--
wpt-commits: df9b1b9549b0c4ca12c18ded12507c497697516c
wpt-pr: 37778
Automatic update from web-platform-tests
Convert html/semantics/forms/the-input-element/email-set-value-ref.html to a ref test. (#37773)
Fixes the issue 37214 by converting this test to a ref test.
getSelection().toString() returning the visible text of input element is
a non-standard Blink/WebKit behavior and should not be relied upon by the test.
--
wpt-commits: a8fcfeb55890d74698d76c6dba15b31ee6c2394f
wpt-pr: 37773
Automatic update from web-platform-tests
[dom] Implement AbortSignal.any() prototype
This adds the basic functionality for AbortSignal.any(), which creates
a new signal that will be aborted if any of the signals associated
signals are aborted. The API is implemented behind a flag.
The general idea and concepts are:
- A signal created with this API is a "composite signal", composed of
0 or more "abort sources".
- An abort source can be any AbortSignal, but since the relationships
are established at signal creation time, we can link to non-composite
signals, i.e. those associated with a controller.
- If any of the abort sources are already aborted when this API is
called, it returns an aborted signal (with the culprit's reason).
- During SignalAbort, a signal will invoke SignalAbort on all of its
"dependent signals" (those for which it is a source).
Most of this is implemented by AbortSignalCompositionManager. In this CL
this class handles linking source/dependent abort signals, but in
follow-up CLs this will also:
1. Also manage priority sources for composite TaskSignals, which are
created by a specialization for TaskSignal.any(). The logic for
managing abort and priority sources/dependents is the same, so this
setup is optimized for code reuse. Note also that the WPT tests for
for AbortSignal.any() are implemented in resources/ and pulled in
via META statements for reuse with TaskSignal.any().
2. Handle more complex memory management. Memory leaks can result from
composite signals following long-lived top-level signals, which we
expect to be a common pattern and part of the motivation for the UA
maintaining the signal relationships. This is separated out to keep
CLs smaller.
Explainer: https://github.com/shaseley/abort-signal-any
I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/FSH6hrJMaxM/m/Ft8KiGlbAAAJ
Design doc: https://docs.google.com/document/d/1LvmsBLV85p-PhSGvTH-YwgD6onuhh1VXLg8jPlH32H4/edit?usp=sharing
Bug: 1323391
Change-Id: Ibc85815b166fd4242543f30600be99fadf35992e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3703640
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1089752}
--
wpt-commits: e8cba6918a23cc46ebfb7c83c7439f3abc0aa973
wpt-pr: 37434
Automatic update from web-platform-tests
Add align-tracks and justify-tracks parsing tests (#37771)
These tests are mainly copies of the align-content and justify-content,
and have been expanded upon to include different track scenarios.
--
wpt-commits: 522047d2680b8a25480d53d1ee7161a60b3fe748
wpt-pr: 37771