Skip to content
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

Merged
merged 1 commit into from
Nov 9, 2016

Conversation

annevk
Copy link
Member

@annevk annevk commented Oct 20, 2016

See whatwg/html#1925 for context.

@wpt-pr-bot
Copy link
Collaborator

Reviewers for this pull request are: @Ms2ger, @ayg, @gsnedders, @jdm, @jgraham, @plehegar, @sideshowbarker, @zcorpan, and @zqzhang.

Copy link
Member

@zcorpan zcorpan left a 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?

@annevk
Copy link
Member Author

annevk commented Oct 20, 2016

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.

foolip added a commit to whatwg/html that referenced this pull request Oct 20, 2016
foolip added a commit to whatwg/html that referenced this pull request Oct 20, 2016
foolip added a commit to whatwg/html that referenced this pull request Oct 20, 2016
zcorpan pushed a commit to whatwg/html that referenced this pull request Oct 20, 2016
annevk added a commit to whatwg/html that referenced this pull request Oct 20, 2016
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.
@ayg ayg closed this Oct 26, 2016
@ayg ayg deleted the annevk/click-in-progress-flag branch October 26, 2016 17:38
@ayg ayg restored the annevk/click-in-progress-flag branch October 26, 2016 18:03
@ayg ayg reopened this Oct 26, 2016
@wpt-stability-bot
Copy link

Firefox

Testing revision 5e74f15
Starting 10 test iterations
No tests run.

@wpt-stability-bot
Copy link

Chrome

Testing revision 5e74f15
Starting 10 test iterations
No tests run.

@foolip
Copy link
Member

foolip commented Nov 9, 2016

The spec change has been merged, is this ready now?

@zcorpan zcorpan merged commit dc79ff5 into master Nov 9, 2016
@zcorpan zcorpan deleted the annevk/click-in-progress-flag branch November 9, 2016 21:36
alice pushed a commit to alice/html that referenced this pull request Jan 8, 2019
alice pushed a commit to alice/html that referenced this pull request Jan 8, 2019
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants