-
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
<form> submission checks #5761
<form> submission checks #5761
Conversation
Simple tests for #3109 and whatwg/html#2615.
Notifying @ayg. (Learn how reviewing works.) |
These tests are now available on w3c-test.org |
Firefox (nightly channel)Testing web-platform-tests at revision 3ea8c23 All results1 test ran/html/semantics/forms/form-submission-0/submission-checks.window.html
|
Chrome (unstable channel)Testing web-platform-tests at revision 3ea8c23 All results1 test ran/html/semantics/forms/form-submission-0/submission-checks.window.html
|
Require that they are all connected to a document that is fully active. There is enough difference between implementations that this appears to be web compatible. Tests: * web-platform-tests/wpt#5758 * web-platform-tests/wpt#5759 * web-platform-tests/wpt#5761 Fixes #2615.
Require that they are all connected to a document that is fully active. There is enough difference between implementations that this appears to be web compatible. Tests: * web-platform-tests/wpt#5758 * web-platform-tests/wpt#5759 * web-platform-tests/wpt#5761 Fixes #2615.
Is this just waiting on a reviewer? |
frame.onload = t.step_func(() => { | ||
if(frame.contentWindow.location.href === "about:blank") | ||
return; | ||
assert_unreached(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the origial navigation to /common/blank.html is expected to be interrupted but the disconnected form submission, but that submission should not actually cause any other navigation to occur either?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's only a single potential navigation here. And it would be due to the form submission, except it shouldn't work as the form is not connected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These tests look fine from a code point of view.
Require that they are all connected to a document that is fully active. There is enough difference between implementations that this appears to be web compatible. Tests: * web-platform-tests/wpt#5758 * web-platform-tests/wpt#5759 * web-platform-tests/wpt#5761 Fixes #2615.
Build PASSEDStarted: 2017-09-15 13:32:57 View more information about this build on: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Ideally we'd test connected vs. in a document tree as well, but that's optional...
Require that they are all connected to a document (except for <a>) that is fully active (including <a>). There is enough difference between implementations that this appears to be web compatible. Also perform a second connected check for <form>. Tests: * web-platform-tests/wpt#5758 * web-platform-tests/wpt#5759 * web-platform-tests/wpt#5761 Fixes #2615 and fixes #2708.
Require that they are all connected to a document (except for <a>) that is fully active (including <a>). There is enough difference between implementations that this appears to be web compatible. Also perform a second connected check for <form>. Tests: * web-platform-tests/wpt#5758 * web-platform-tests/wpt#5759 * web-platform-tests/wpt#5761 Fixes whatwg#2615 and fixes whatwg#2708.
Simple tests for #3109 and whatwg/html#2615.