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

Default drag.touchable should use navigator.maxTouchPoints, if supported? #47

Closed
Herst opened this issue Jan 29, 2018 · 3 comments
Closed

Comments

@Herst
Copy link
Contributor

Herst commented Jan 29, 2018

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)")?)

@Herst Herst changed the title Touch detection changes in desktop Chrome Upcoming touch detection changes in desktop Chrome Feb 11, 2018
@altocumulus
Copy link

With the release of Chrome v70 this seems to have become an issue: "Touch handling completely broken on Chrome version 70".

@mbostock
Copy link
Member

mbostock commented Nov 9, 2018

You can use drag.touchable(navigator.maxTouchPoints) or similar if you want to change how d3-drag detects support for touch.

@Herst
Copy link
Contributor Author

Herst commented May 15, 2019

@mbostock 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
Labels
None yet
Development

No branches or pull requests

3 participants