Uncaught TypeError: Cannot read property 'blur' of null
See original GitHub issueI captured events on an react app (using the antd
component library) and if I change an input text, I get the error during playback (using cdn rr-webplayer@latest
with basically just the example code from the guide).
Uncaught TypeError: Cannot read property 'blur' of null
at e.applyIncremental (index.js:1)
at i (index.js:1)
at Object.doAction (index.js:1)
at r (index.js:1)
It stops the playback, but if I click play again, it will continue (although after I can’t replay it again).
The code base is for a private client so I can’t share for replay events (will try to reproduce with sharable code alter)… Just wondering if you have any ideas why this might happen?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Error: Cannot read property 'blur' of undefined - Stack Overflow
I'm trying to implement wheelColorPicker, and I came up with a problem only when using a JQuery version later than 1.7.1. (I'm currently...
Read more >"Cannot read property 'blur' of null" on click · Issue #762 - GitHub
After doing a click on a button, this error is logged in the console, and nothing happens - the page just hangs. I'm...
Read more >Uncaught TypeError: Cannot read property of null - iDiallo
This error occurs when you read a property or call a method on a null object . That's because the DOM API returns...
Read more >Cannot read properties of null (reading 'blur') when I try to get ...
Cannot read properties of null (reading 'blur') message comes up when I try to get IRS form. 0. 2 comments. Copy this post's...
Read more >uncaught typeerror: cannot read properties of null ... - You.com
The "Cannot read property 'forEach' of undefined" error often occurs when trying to access an array index that doesn't exist. index.js const arr...
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
@ChuckJonas Yes, you are right. Because we can not find what cause this without a reproducible events log, so the best thing we can do is to add some safe check and prevent an exception stop the whole world. Previously I do not do this because I want to see whether there is some corner case rrweb does not cover, and a not handled error may encourage users to report the bug. But now more people are trying to use rrweb in production, so safe check and warning messages are more suitable.
Ill give this a go tomorrow if the author didnt fix it already 🙃