-
Notifications
You must be signed in to change notification settings - Fork 47.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
RFC Pointer events #1375
Comments
@zpao Right, saw that issue and forgot about it apparently. It's basically the same discussion, I guess the difference now is that it's becoming a proper standard, meaning there's no reason to support the prefixed events and with |
Can we close this issue and keep going in #499 ? We should just go ahead and adding these. A lower-level polyfill might be able to take over if we just allow the events to be added. |
@syranide Yes please :) |
@sebmarkbage For sure |
http://handjs.codeplex.com/
Stumbled across this a few days ago, MS is seemingly pushing for it to become a standard and looking at other solutions/implementations they seem to align. http://www.w3.org/TR/pointerevents/
Practically it seems like a great thing to support, even if React doesn't provide a core polyfill. Simply adding support for the events so that users are free to polyfill themselves using a library of their choice seems like a great thing.
I don't mind providing a PR (should be a simple matter) if you agree.
The text was updated successfully, but these errors were encountered: