Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Activation behavior doesn't necessarily result in a click event in browsers... #653

Closed
travisleithead opened this issue Oct 27, 2016 · 2 comments

Comments

@travisleithead
Copy link
Member

From #637

Action item is to note an at-risk item for the section about firing an event for activation, as we intend to keep that in the spec, but want to be clear that it's not implement that way by all UAs...

We should create some tests for these if they don't already exist.

@travisleithead
Copy link
Member Author

@chaals wrote:

@travisleithead I'm not sure there is a lot of controversy here. Changing browsers to start firing an extra event on fairly common things seems really risky, so much as I wish (and wished for the last couple of decades) they had already done what the spec asked, I doubt I would wish for that now.
So I am more inclined to just axe the spec-fiction and start thinking about smart ways to solve the problem that will work.

That works too.

@patrickhlauke
Copy link
Member

For cross-reference: whatwg/html#1952 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants