Skip to content

fix(docs): drop browser-extension errors before ingestion - #569

Draft
posthog-eu[bot] wants to merge 1 commit into
mainfrom
posthog-self-driving/fixdocs-filter-browser-extension-errors-f281ed
Draft

fix(docs): drop browser-extension errors before ingestion#569
posthog-eu[bot] wants to merge 1 commit into
mainfrom
posthog-self-driving/fixdocs-filter-browser-extension-errors-f281ed

Conversation

@posthog-eu

@posthog-eu posthog-eu Bot commented Aug 12, 2026

Copy link
Copy Markdown

🔗 Linked issue

No open issue tracks this; found through error tracking.

📚 Description

Problem

  • The docs site owner gets an unactionable issue in the error tracking inbox that reopens for any visitor whose browser runs the extension — the site pays in noise, no user is hurt.
  • A browser extension injected a content script into a docs page and its uncaught error (Invalid call to runtime.sendMessage(). Tab not found.) was captured. runtime.sendMessage is a WebExtension API a page cannot reach, so the thrower is not site code.
  • capture_exceptions: true with no before_send grabs every uncaught error on the page, including ones from code the site does not own.
  • Observed as a burst from one visitor in one session on Mobile Safari / iOS, with no stack frames.

Change

  • Add a before_send hook that drops $exception events originating in an extension context, on two tells:
Tell Match
Extension stack frame frame filename starts with chrome-extension://, moz-extension://, safari-web-extension://
Extension-only API in message exception type/value contains runtime.sendMessage, chrome.runtime, browser.runtime
  • The message match is what catches this issue, since the event carries no frames.
  • Site pageviews, analytics, and site-owned exceptions are untouched.

Alternative considered

  • An error tracking suppression rule hides this one fingerprint faster but does nothing about the next extension error; the filter stops the whole class at the source.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

Created with PostHog Desktop from this inbox report.

Generated-By: PostHog Desktop
Task-Id: 693a7a10-08da-4bf1-8063-b427fa4532be
@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 001b76e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
evlog-docs Ready Ready Preview, v0 Aug 12, 2026 10:53pm
evlog-render-lab Ready Ready Preview Aug 12, 2026 10:53pm
3 Skipped Deployments
Project Deployment Actions Updated (UTC)
evi Skipped Skipped Aug 12, 2026 10:53pm
evlog-telemetry Skipped Skipped Aug 12, 2026 10:53pm
just-use-evlog Skipped Skipped Aug 12, 2026 10:53pm

Request Review

@github-actions github-actions Bot added the bug Something isn't working label Aug 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@pkg-pr-new

pkg-pr-new Bot commented Aug 12, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/@evlog/cli@569
npm i https://pkg.pr.new/evlog@569
npm i https://pkg.pr.new/@evlog/nuxthub@569
npm i https://pkg.pr.new/@evlog/telemetry@569

commit: 001b76e

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

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants