Sync WPT with upstream (14-09-2025) (#39293)

Automated downstream sync of changes from upstream as of 14-09-2025
[no-wpt-sync]

Signed-off-by: WPT Sync Bot <ghbot+wpt-sync@servo.org>
This commit is contained in:
Servo WPT Sync 2025-09-14 03:44:16 +02:00 committed by GitHub
parent 3ef3ba9378
commit b3b79e049b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
308 changed files with 6147 additions and 1657 deletions

View file

@ -4,3 +4,6 @@
[Tests FormControlRange default values when no form control is set.]
expected: FAIL
[FormControlRange handles empty value correctly.]
expected: FAIL

View file

@ -0,0 +1,33 @@
[FormControlRange-offset.html]
[FormControlRange with single character in textarea.]
expected: FAIL
[FormControlRange with empty control in textarea.]
expected: FAIL
[FormControlRange boundary positions in textarea.]
expected: FAIL
[FormControlRange with Unicode characters in textarea.]
expected: FAIL
[FormControlRange with single character in input.]
expected: FAIL
[FormControlRange with empty control in input.]
expected: FAIL
[FormControlRange boundary positions in input.]
expected: FAIL
[FormControlRange with Unicode characters in input.]
expected: FAIL
[FormControlRange preserves whitespace in textarea light DOM.]
expected: FAIL
[FormControlRange should work correctly with weirdly formed light DOM structure.]
expected: FAIL
[FormControlRange ignores malformed input child nodes.]
expected: FAIL

View file

@ -0,0 +1,15 @@
[FormControlRange-range-updates.html]
[FormControlRange allows updating range on same element.]
expected: FAIL
[FormControlRange can switch between different form controls.]
expected: FAIL
[FormControlRange works with disconnected and then connected form controls.]
expected: FAIL
[FormControlRange can switch between connected and disconnected form controls.]
expected: FAIL
[FormControlRange reflects value changes on same element.]
expected: FAIL

View file

@ -0,0 +1,18 @@
[FormControlRange-supported-elements.html]
[FormControlRange should support textarea.]
expected: FAIL
[FormControlRange should support input[type=text\].]
expected: FAIL
[FormControlRange should support input[type=search\].]
expected: FAIL
[FormControlRange should support input[type=password\].]
expected: FAIL
[FormControlRange should support input[type=url\].]
expected: FAIL
[FormControlRange should support input[type=tel\].]
expected: FAIL

View file

@ -0,0 +1,15 @@
[FormControlRange-toString.html]
[FormControlRange toString() reflects current value.]
expected: FAIL
[FormControlRange toString() clamps to available length.]
expected: FAIL
[FormControlRange toString() handles value shorter than range.]
expected: FAIL
[FormControlRange toString() handles auto-collapsed backwards ranges.]
expected: FAIL
[FormControlRange uses current input.value, not value attribute.]
expected: FAIL

View file

@ -0,0 +1,12 @@
[FormControlRange-unsupported-elements.html]
[FormControlRange throws NotSupportedError for text node.]
expected: FAIL
[FormControlRange should throw NotSupportedError for all unsupported HTML5 elements.]
expected: FAIL
[FormControlRange should throw NotSupportedError for unsupported input types.]
expected: FAIL
[NotSupportedError should take precedence over IndexSizeError when both element type and index are invalid for a FormControlRange.]
expected: FAIL

View file

@ -0,0 +1,6 @@
[FormControlRange-validation.html]
[FormControlRange preserves state when setFormControlRange throws.]
expected: FAIL
[FormControlRange handles all range types correctly: forward, backwards, and out-of-bounds.]
expected: FAIL