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

interactionID should be harmonized with activation triggering input events #105

Closed
annevk opened this issue Sep 27, 2021 · 6 comments
Closed

Comments

@annevk
Copy link
Member

annevk commented Sep 27, 2021

https://html.spec.whatwg.org/#activation-triggering-input-event

Seems bad to have multiple sources of what is considered a user interaction.

@npm1
Copy link
Collaborator

npm1 commented Sep 27, 2021

It seems hard to reconcile the two. For instance we care about keyboard events, and those are not activation triggering.

@annevk
Copy link
Member Author

annevk commented Sep 28, 2021

Well, I think in implementations they are. See whatwg/html#3849.

@npm1
Copy link
Collaborator

npm1 commented Sep 28, 2021

It sounds like maybe some, but not all. I don't think we'd want to special-case the Esc key for performance measurement whereas it makes sense to consider it different for the user activation scenario. So although I agree there is a wide overlap, I think they're not quite the same.

@npm1
Copy link
Collaborator

npm1 commented Dec 22, 2021

Ok to close this?

@annevk
Copy link
Member Author

annevk commented Jan 3, 2022

Yeah I guess so, though I'm still a bit wary about maintaining a generic list like this in such a specific document. Is the plan to uplift this to UI Events?

@npm1
Copy link
Collaborator

npm1 commented Jan 10, 2022

It is only used here for now, but we can move it to UI Events if anything to make it more discoverable. Filed #114

@npm1 npm1 closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants