fix(web): filter benign ResizeObserver loop warning from PostHog - #2783
Merged
Conversation
Chrome/Firefox report "ResizeObserver loop completed with undelivered notifications." via window.onerror even though nothing threw. PostHog's capture_unhandled_errors picks it up and reports it as a real exception. Add it to the existing droppable-exception filter alongside the other known-benign browser signatures. Co-Authored-By: Claude Sonnet 5 <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.
Summary
ResizeObserver loop completed with undelivered notifications.was showing up as a tracked error.window.onerrorwhen aResizeObservercallback can't finish its notification cycle within one frame. Nothing actually threw. Since PostHog'scapture_unhandled_errorslistens onwindow.onerror, it was picked up and reported as a real exception.ResizeObserver loop limit exceeded) to the existing droppable-exception filter, alongside the other known-benign browser signatures already filtered there (CefSharp scanner noise, opaque cross-originScript error., SuperTokens network blips).Investigation also found several likely sources of the observer activity (grid measurement hooks with a measure→setState→resize cycle, floating-ui
autoUpdateon tooltips/menus) — these are expected in an app with dynamic, size-driven layout and not something to remove; only the reporting-side false positive is fixed here.Simplicity
Minimal fix: two string constants + one conditional check, following the exact existing pattern in
posthog-exception-filter.util.ts(no new abstractions, no changes to the layout/observer code).Automated validation
N/A — this is error-filtering config, not a UI change; no browser-observable behavior to verify.
Independent review
Not run for this change.
Test plan
TZ=UTC NODE_ENV=test bun test ./src/auth/posthog/posthog-exception-filter.util.test.ts(frompackages/web) — 12 pass, 0 fail (2 new tests added)bun run type-check— clean