Automatic update from web-platform-tests
[css-nesting] Add CSSOM support for nested style rules.
Allow CSSStyleRule to have child rules, which we can inspect,
add and delete.
This allows us to do easier testing from JavaScript, so we do
an overhaul of the WPT tests. They are moved into a new directory
css-nesting/, we split out the parts we don't support right now
(properties directly in conditional rules) into new tests,
add invalidation tests, and finally some CSSOM tests.
Bug: 1095675
Change-Id: Iaffd2a2820b75a57924b474868724eeef430df7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963170
Commit-Queue: Rune Lillesveen <[email protected]>
Reviewed-by: Rune Lillesveen <[email protected]>
Auto-Submit: Steinar H Gunderson <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1061220}
--
wpt-commits: 4eea9bf182441d01a4c91cf7b08d8bdef7a9c38f
wpt-pr: 36520
Automatic update from web-platform-tests
Replace some "assert_throws(new FooError(), stuff)" calls with assert_throws_js. (#21354)
This diff was generated by running:
find . -type f -print0 | xargs -0 perl -pi -e 'BEGIN { $/ = undef; } s/assert_throws\(([ \n]*)new ([A-Za-z]*Error) *\(\) *(, *.)/assert_throws_js(\1\2\3/gs'
and then:
1) Manually adjusting fullscreen/rendering/fullscreen-pseudo-class-support.html
to test for the right sort of exceptions ("SyntaxError" DOMException, not a JS
SyntaxError).
2) Manually adjusting performance-timeline/po-observe-type.any.js to test for
the right sort of exceptions ("SyntaxError" DOMException, not a JS
SyntaxError).
3) Manually adjusting performance-timeline/po-observe.any.js to test for
the right sort of exceptions ("SyntaxError" DOMException, not a JS
SyntaxError).
4) Manually adjusting user-timing/mark_exceptions.html to test for the right
sort of exceptions ("SyntaxError" DOMException, not a JS SyntaxError).
5) Manually adjusting user-timing/measure_syntax_err.any.js to test for the right
sort of exceptions ("SyntaxError" DOMException, not a JS SyntaxError).
6) Manually adjusting domxpath/lexical-structure.html to test for a
"SyntaxError" DOMException, since that's what all browsers throw and there is no
clear spec for this.
7) Manually adjusting workers/constructors/Worker/Worker-constructor.html to
test for the right sort of exceptions ("SyntaxError" DOMException, not a JS
SyntaxError).
8) Backing out the changes to resources/idlharness.js because some tests pass
objects from a different window to it, and we end up with the wrong TypeError
constructor in those cases.
This does affect indentation poorly in cases when the first arg was on the same
line as the assert_throws, there was a newline after the ',' after the first
arg, and the following args were lined up with the first arg. Fixing that,
especially when there are multiple lines after the first arg, is not trivial
with a regexp.
Co-authored-by: Boris Zbarsky <[email protected]>
Co-authored-by: Stephen McGruer <[email protected]>
--
wpt-commits: 2c5c3c4c27d27a419c1fdba3e9879c2d22037074
wpt-pr: 21354