You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my app press cmd+backspace on any non-empty line in a contentEditable div. Unfortunately my app's not public yet.
Testcase Gist URL
No response
Additional Information
I use rrweb thru PostHog session replay and capture all backtraces from the window error event. Because whatever loads this script (I presume PostHog?) loads it without crossorigin set I initially just got a "Script error." error event. It was reproducing locally with the debugger open that I got the aforementioned error and tracked it down to the aforementioned line.
The text was updated successfully, but these errors were encountered:
To keep this issue alive, many of our customers have also reported seeing this error. We are using the same version noted above in our instrumentation library.
⬆️ The way New Relic is currently planning on circumventing this until a bigger fix is implemented is to intercept the error using rrweb's errorHandler configuration, and flagging the error object in such a way as to not report it as a customer-based error.
Preflight Checklist
What package is this bug report for?
rrweb
Version
2.0.0-alpha.12
Expected Behavior
No uncaught exceptions.
Actual Behavior
There is an uncaught exception triggering the window
error
event:on this line:
rrweb/packages/rrweb/src/record/mutation.ts
Line 444 in 3d1877c
Steps to Reproduce
In my app press cmd+backspace on any non-empty line in a contentEditable div. Unfortunately my app's not public yet.
Testcase Gist URL
No response
Additional Information
I use rrweb thru PostHog session replay and capture all backtraces from the window error event. Because whatever loads this script (I presume PostHog?) loads it without
crossorigin
set I initially just got a "Script error." error event. It was reproducing locally with the debugger open that I got the aforementioned error and tracked it down to the aforementioned line.The text was updated successfully, but these errors were encountered: