Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove event listeners affecting scrolling performance
See original GitHub issueSome touch and wheel related listeners can affect scrolling performance, find a way to resolve these either by removing them or by using preventDefault in them. These were reported by the Lighthouse Best Practices (https://web.dev/uses-passive-event-listeners/)
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Use passive listeners to improve scrolling performance
Learn how to improve your page's scrolling responsiveness by avoiding passive event listeners.
Read more >Optimizing JavaScript Event Listeners for Performance
Scroll Events with Passive Event Listeners It enables developers to opt-in to better scroll performance by eliminating the need for scrolling to block...
Read more >Does adding too many event listeners affect performance?
But the original question seems to be more concerned about the performance impact of triggering those event handlers (e.g. click or scroll ......
Read more >Use passive listeners to improve scrolling performance
This may introduce an undesired effect called scroll jank, where the page stutters or doesn't respond smoothly to user inputs.
Read more >Lighthouse says: Does not use passive listeners to improve ...
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. URL, Location. /5.6.3/bundle.min.js( ...
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 Free
Top 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
I am unable to solve this issue
@DubeySandeep, this has been fixed for all pages with the exception of exploration player and editor because guppy is used in these pages and guppy requires the listeners to not be passive.