-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Test same-value-setting not changing selection for input/textarea #5147
Conversation
These tests are now available on w3c-test.org |
Firefox (nightly channel)Testing web-platform-tests at revision 6b2d0a5 All results1 test ran/html/semantics/forms/textfieldselection/selection-after-content-change.html
|
Chrome (unstable channel)Testing web-platform-tests at revision 6b2d0a5 All results1 test ran/html/semantics/forms/textfieldselection/selection-after-content-change.html
|
- Expand coverage to include .focus() - Allow either "none" or "forward" selection direction - Test normalization a bit more
*This report has been truncated because the total content is 1612497 characters in length, which is in excess of GitHub.com's limit for comments (65536 characters). Firefox (nightly channel)Testing web-platform-tests at revision 79e4b2e All results112 tests ran/2dcontext/pixel-manipulation/2d.imageData.create2.double.html
/2dcontext/pixel-manipulation/2d.imageData.create2.zero.html
/2dcontext/pixel-manipulation/2d.imageData.get.double.html
/2dcontext/pixel-manipulation/2d.imageData.get.zero.html
/FileAPI/historical.https.html
/IndexedDB/idbobjectstore_createIndex15-autoincrement.htm
/XMLHttpRequest/send-conditional-cors.htm
/XMLHttpRequest/send-conditional.htm
/content-security-policy/connect-src/connect-src-beacon-blocked.sub.html
/content-security-policy/connect-src/connect-src-eventsource-blocked.sub.html
/content-security-policy/connect-src/connect-src-websocket-blocked.sub.html
/content-security-policy/connect-src/connect-src-xmlhttprequest-blocked.sub.html
/content-security-policy/inside-worker/dedicated-inheritance.html
/content-security-policy/inside-worker/dedicated-script.html
/content-security-policy/inside-worker/shared-inheritance.html
/content-security-policy/inside-worker/shared-script.html
/content-security-policy/securitypolicyviolation/securitypolicyviolation-block-cross-origin-image-from-script.sub.html
/content-security-policy/securitypolicyviolation/securitypolicyviolation-block-cross-origin-image.sub.html
/content-security-policy/securitypolicyviolation/securitypolicyviolation-block-image-from-script.sub.html
/content-security-policy/securitypolicyviolation/securitypolicyviolation-block-image.sub.html
/content-security-policy/worker-src/dedicated-child.sub.html
/content-security-policy/worker-src/dedicated-fallback.sub.html
/content-security-policy/worker-src/dedicated-list.sub.html
/content-security-policy/worker-src/dedicated-none.sub.html
/content-security-policy/worker-src/dedicated-self.sub.html
/content-security-policy/worker-src/service-child.https.sub.html
/content-security-policy/worker-src/service-fallback.https.sub.html
/content-security-policy/worker-src/service-list.https.sub.html
/content-security-policy/worker-src/service-none.https.sub.html
/content-security-policy/worker-src/service-self.https.sub.html
/content-security-policy/worker-src/shared-child.sub.html
/content-security-policy/worker-src/shared-fallback.sub.html
/content-security-policy/worker-src/shared-list.sub.html
/content-security-policy/worker-src/shared-none.sub.html
/content-security-policy/worker-src/shared-self.sub.html
/cors/preflight-failure.htm
/dom/events/EventTarget-dispatchEvent.html
/dom/nodes/Document-createEvent.html
|
Chrome (unstable channel)Testing web-platform-tests at revision 79e4b2e |
lgtm |
@domenic it doesn't look like there are any tests here exercising the situation when https://html.spec.whatwg.org/multipage/forms.html#value-sanitization-algorithm modifies the value, right? It's not quite obvious to me whether "new value" as used in the setter of the "value" mode at https://html.spec.whatwg.org/multipage/forms.html#dom-input-value in step 5 means the string that was passed to the setter or the string after application of the value sanitization algorithm, and the lack of tests makes it likely UAs would end up with differing interpretations there. Ideally we would both test the behavior and define it more clearly in the spec. |
This is a follow-up to #2437, which introduced the value comparison and its impact on selection. See web-platform-tests/wpt#5147 (comment).
This is a follow-up to #5147. It tests the clarification at whatwg/html#2560. While there, it also adds additional textarea test cases for line-ending normalization; previously the test only tested an in-document textarea.
This is a follow-up to #2437, which introduced the value comparison and its impact on selection. See web-platform-tests/wpt#5147 (comment).
This is a follow-up to #5147. It tests the clarification at whatwg/html#2560. While there, it also adds additional textarea test cases for line-ending normalization; previously the test only tested an in-document textarea.
This is a follow-up to whatwg#2437, which introduced the value comparison and its impact on selection. See web-platform-tests/wpt#5147 (comment).
This is a follow-up to whatwg#2437, which introduced the value comparison and its impact on selection. See web-platform-tests/wpt#5147 (comment).
This is a follow-up to whatwg#2437, which introduced the value comparison and its impact on selection. See web-platform-tests/wpt#5147 (comment).
Follows whatwg/html#2437.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)