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
Default drag.touchable should use navigator.maxTouchPoints, if supported? #47
Comments
Herst
changed the title
Touch detection changes in desktop Chrome
Upcoming touch detection changes in desktop Chrome
Feb 11, 2018
With the release of Chrome v70 this seems to have become an issue: "Touch handling completely broken on Chrome version 70". |
You can use |
Closed
Firefox followed suit: https://bugzil.la/1412485 (see also https://www.fxsitecompat.com/en-CA/docs/2019/legacy-touch-events-api-is-now-disabled-on-desktop/) |
mbostock
changed the title
Upcoming touch detection changes in desktop Chrome
Default drag.touchable should use navigator.maxTouchPoints, if supported?
Aug 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://crbug.com/392584
No idea what d3.js could or should do about it, probably do nothing and just add a note to the documentation of
drag.touchable
?(Or use
navigator.maxTouchPoints
/window.matchMedia("(any-pointer)")
?)The text was updated successfully, but these errors were encountered: