-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
a-scene Chrome non-passive violation warnings for touchmove and touchstart event handlers #5510
Comments
Thanks for reporting, interestingly enough I wasn't able to reproduce the warnings locally only in deployed versions. In any case, I've created a PR that sets the |
Interesting. I can't see the warnings on Chrome 123 for Mac (neither locally served or deployed versions). It looks warnings should have been seen since Chrome 51. What should I do to reproduce? |
@dmarcos What worked for me was on desktop Chrome 122 visiting https://aframe.glitch.me/, opening the dev console and then refreshing. They didn't show up for me when opening the dev tools after page load, nor did they show up on Quest or Android smartphone with remote debugging. And never showed up locally for some reason. Hope this helps, no idea why this warning is so elusive. |
Can't reproduce either on the glitch. Would be interesting to understand a bit more. |
Description:
For a simple scene, Chrome is logging these warnings to the console:
The error references: https://www.chromestatus.com/feature/5745543795965952
Links referred to in console for 1.5.0:
I think all you need to reproduce it is a
<a-scene />
- but here's an example using look-controls too:The text was updated successfully, but these errors were encountered: