-
-
Notifications
You must be signed in to change notification settings - Fork 35.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
OrbitControls eats touch events? #16254
Comments
Does it work if you remove |
Yes, removing |
see #13706 (comment) @WestLangley Maybe it's better to remove the usage of @arodic What do you think about this issue? |
I've typically gotten around this by setting the element.addEventListener( 'mousedown', onMouseDown, true ); It's not super convenient but it does guarantee that your function will get called before the controls callback that stops the propagation. I would be for an option that enables or disables the event "eating" behavior or just removing it entirely. |
I am reluctant to support further modifications to |
Closing, see #18612 (comment). |
For anyone having the same issue: Just use pointer events ( OrbitControls uses these and calls
|
I have an app that uses raycaster for clicking shapes and Orbit Controls.
An older version of OrbitControls (don't know the version, probably r79, from 2017-02-11) works fine on mobile, but the new version (r103) seems to be eating touch events, as they are no longer picked by the app. Interestingly, mouse events work.
The interactivity examples on three.js work fine too, but they use TrackControls.
The text was updated successfully, but these errors were encountered: