-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to read the 'contentDocument' property on older browsers => broken page #14313
Closed
3 tasks done
Closed
3 tasks done
Labels
Package: react
Issues related to the Sentry React SDK
Comments
Yep catching sounds good to me here, I'll open up a pr today |
The error is still showing up on 8.40.0. Looking at the source of it, it seems to be coming from https://github.com/getsentry/rrweb. Maybe rrweb was not bumped within sentry-javascript? |
@jlowcs Yeah it hasn't been bumped yet, will let you know when we do |
@jlowcs This should be released now in 8.43.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/react
SDK Version
8.36.0
Framework Version
react 18.3.1
Link to Sentry event
https://changeorg.sentry.io/issues/6048039184/events/9fa3cc0ed21f4efab1dd24971ce140b0/
Reproduction Example/SDK Setup
No response
Steps to Reproduce
Hard to say.
We are noticing some
Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "..."
errors coming from older browsers. This results in a broken page for us.My guess is that those older browsers are throwing a
SecurityError
instead of returningnull
when accessing aiframe.contentDocument
on an iframe that is hiding its content to Sentry (in this case a Stripe iframe).This specific error is coming from this line, but there might be other instances of this accessor within the Sentry code.
Expected Result
Sentry should catch that error instead of letting it bubble.
Something like this:
Actual Result
Error is thrown and is breaking the page.
The text was updated successfully, but these errors were encountered: