Conversation
The "Error: frame window is not ready" is thrown by third-party scripts or browser internals when accessing iframe.contentWindow before the frame has finished loading. The error string does not exist in the source code or any dependency, confirming it originates from external code. These errors are not actionable and create noise in Sentry. Closes #8384 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8384
Summary
beforeSendfilter to drop "frame window is not ready" errorsiframe.contentWindowbefore the frame is loaded — the exact string does not exist in our source code or any dependencyTest plan
beforeSendyarn testpasses (160 suites, 1550 tests)🤖 Generated with Claude Code