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.
Chrome 56 and later, warning with preventDefault, react issue
See original GitHub issueSyntheticEvent.js:115 Unable to preventDefault inside passive event listener due to target being treated as passive. See https://www.chromestatus.com/features/5093566007214080
Actually I don’t know what is this. I will investigate.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7
Top Results From Across the Web
Chrome 56 breaks touch events · Issue #8968 · facebook/react
React attaches events to the document node which causes the latest version ... Chrome 56 and later, warning with preventDefault, react issue ......
Read more >Easy fix for: Unable to preventDefault inside passive event ...
1. Remove the need for preventDefault() in the event listener · 2. Mark the event listener not the be passive (not recommended).
Read more >Unable to preventDefault inside passive event listener
here is my solution for react. this is for silly react number textfield scrolling problem which causes number change while moving ...
Read more >Making touch scrolling fast by default - Chrome Developers
In Chrome 56 and later, DevTools will log a warning when you call preventDefault() in an event where the intervention is active.
Read more >React Axios API Requests | Axios with React JS Tutorial
Learn React Axios API Requests in this tutorial. We will implement Axios with React JS as we build our React JS Blog project....
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
track via React discussion about this facebook/react#8968
@MikeLP would you happen to have thoughts on #69 ?
proposing changing
preventDefaultprop to default to false in v4 because of this chrome change