-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
form-associated custom elements and their ElementInternals #25705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Heads up! This PR modifies the following files:
|
|
Opened new PR for upstreamable changes. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
0ffa292 to
29d8bf9
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
29d8bf9 to
76315b5
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
|
I made an incidental change to a shared test .js file that might have repercussions. |
sketching ElementInternals Form-associated elements are now working. Remaining test failures in custom-elements/form-associated/ are: * whatwg/html#4658 hasn't made it into the standard yet, and ElementInternals-accessibility is all about that functionality. * ElementInternals-setFormValue hits many race conditions with our iframe order of operations. Isolating just the "submit this form with these custom elements, look at the query" part, the payload of each test actually does pass! Running the tests as written, we end up with different tests overwriting each other's elements and getting very confused. One problem is the about:blank double-load-event thing, but fixing that doesn't fix everything. * ElementInternals-validation doesn't work because we don't have form validation in general; I've commented the relevant stubs. * ElementInternals-form-disabled-callback fails on #25713.
|
PR title changed; changed existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
|
💔 Test failed - status-taskcluster |
|
Just the usual new-exposed-functionality-exists tests I invariably forget to update the metadata for on my first try. |
76315b5 to
0086bda
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
0086bda to
e703949
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
e703949 to
5917dfd
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
|
web-platform-tests/wpt#21747 just merged; I'll adjust for it in the morning. |
|
I'll also add a _mozilla version of the setFormValue test that works serially and doesn't race iframe loads against promise reactions. |
|
☔ The latest upstream changes (presumably #25674) made this pull request unmergeable. Please resolve the merge conflicts. |
5917dfd to
a82d56e
Compare
|
Transplanted upstreamable changes to existing PR. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21678. |
|
☔ The latest upstream changes (presumably #25783) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Closing this in favor of #31980. |
Form-associated elements are now working.
Remaining test failures in custom-elements/form-associated/ are:
fix #24988 fix #25015 fix #25017