-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Manual test for click in progress flag #4034
Conversation
See whatwg/html#1925 for context.
Reviewers for this pull request are: @Ms2ger, @ayg, @gsnedders, @jdm, @jgraham, @plehegar, @sideshowbarker, @zcorpan, and @zqzhang. |
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.
Should we hold on merging this until the spec change is merged?
Yeah maybe, would be good if @foolip wrote down the guidelines for that somewhere. And maybe we should add a WPT label for that kind of thing too. |
Prompted by web-platform-tests/wpt#4034. Part of #1849.
Prompted by web-platform-tests/wpt#4034. Part of #1849.
Prompted by web-platform-tests/wpt#4034. Part of #1849.
Prompted by web-platform-tests/wpt#4034. Part of #1849.
There are two major changes here: * Any click event can cause activation behavior to run. No exceptions. * The "click in progress flag" is now restricted to the click() method, as it already is in Firefox. The other changes are editorial: * "Activation behavior" is now associated with an object at all times (and cannot be conditionally associated) * "Legacy-pre-activation behavior" and "legacy-canceled-activation behavior" are now more clearly only relevant for input elements in either the Checkbox or Radio Button state. * Various concepts such as "run synthetic click activation steps" and "nearest activatable element" are gone as they are obsoleted by the DOM Standard or the aforementioned normative changes. Tests related to this change: * web-platform-tests/wpt#3974 * web-platform-tests/wpt#4034 Changes to the DOM Standard that were necessary for this change: * whatwg/dom#342 * whatwg/dom#346 Fixes #1394.
FirefoxTesting revision 5e74f15 |
ChromeTesting revision 5e74f15 |
The spec change has been merged, is this ready now? |
Prompted by web-platform-tests/wpt#4034. Part of whatwg#1849.
There are two major changes here: * Any click event can cause activation behavior to run. No exceptions. * The "click in progress flag" is now restricted to the click() method, as it already is in Firefox. The other changes are editorial: * "Activation behavior" is now associated with an object at all times (and cannot be conditionally associated) * "Legacy-pre-activation behavior" and "legacy-canceled-activation behavior" are now more clearly only relevant for input elements in either the Checkbox or Radio Button state. * Various concepts such as "run synthetic click activation steps" and "nearest activatable element" are gone as they are obsoleted by the DOM Standard or the aforementioned normative changes. Tests related to this change: * web-platform-tests/wpt#3974 * web-platform-tests/wpt#4034 Changes to the DOM Standard that were necessary for this change: * whatwg/dom#342 * whatwg/dom#346 Fixes whatwg#1394.
See whatwg/html#1925 for context.