Console warnings for non-passive scroll event handlers
See original GitHub issueThere is an issue with Chrome showing warnings for all slick components. It is related to non-passive scroll event listeners.
To reproduce, just load the demo page and see the many warnings like this:
[Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive.
For more info, see this: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener
Issue Analytics
- State:
- Created 6 years ago
- Reactions:22
- Comments:22
Top Results From Across the Web
Console warnings for non-passive scroll event handlers
I'm using google chrome. [Violation] Added non-passive event listener to a scroll-blocking 'mousewheel' event. Consider marking event handler as ...
Read more >Excessive console warnings for non-passive scroll event ...
Hi, I'm experiencing a weird bug. I have a simple slider component on a webpage. It all works fine, but when accessing the...
Read more >Console warnings for non-passive scroll event handlers-Vue.js
[Solved]-Console warnings for non-passive scroll event handlers-Vue.js ... There is a new options object that can be passed to the addEventListener . The...
Read more >Non-passive event listener warning in Chrome console - v6
I am using React with a custom component to mount/unmount CodeMirror to the page. I don't think that would be the issue, but...
Read more >scrollbar Non Passive Event Listener Error
I getting warning like this on my chrome console..as. [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This seems to still be happening, any updates?
same issue here! any updates?