Skip to content

Conversation

@billyvg
Copy link
Member

@billyvg billyvg commented Jun 13, 2024

Do not attempt to access contentDocument of iframe if element is blocked, otherwise it will trigger a browser warning. e.g.

Blocked a frame with origin "<foo>" from accessing a frame with origin "<bar>". Protocols, domains, and ports must match.

Fixes getsentry/sentry-javascript#6560

…ontentDocument`

Do not attempt to access `contentDocument` of iframe if element is blocked, otherwise it will trigger a browser warning. e.g.

`Blocked a frame with origin "<foo>" from accessing a frame with origin "<bar>". Protocols, domains, and ports must match.`
@billyvg billyvg marked this pull request as ready for review June 13, 2024 16:27
@billyvg billyvg requested a review from a team June 13, 2024 16:29
Copy link
Member

@mydea mydea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ahh very nice catch, that makes sense!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Customer issue: "Blocked a frame with origin <hostname> from accessing a cross-origin frame."

3 participants