Back to feed
Dev.to
Dev.to
7/15/2026
Why Chrome extensions cannot intercept service-worker push notifications from third-party sites

Why Chrome extensions cannot intercept service-worker push notifications from third-party sites

Original: I spent a week trying to intercept Slack push notifications from a Chrome extension. Here's why it's impossible.

Short summary

A developer explains why Chrome extensions cannot intercept push notifications fired from third-party service workers. Service workers run in isolated threads with no access to the page's window object, and the Chrome Extensions API provides no mechanism to inject code into arbitrary service worker scopes. Three workaround approaches were investigated, including the chrome.debugger API with CDP, but each has significant limitations or UX tradeoffs that make reliable interception impractical.

  • •Service workers run in isolated threads with no window object, making MAIN world overrides ineffective for push notifications
  • •Chrome Extensions API offers no mechanism to inject code into third-party service worker scopes — a hard security boundary
  • •The chrome.debugger API with CDP can technically intercept SW scripts but triggers visible debugging warnings to users

Generated with AI, which can make mistakes.

Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

Building a keyword-filtered notification reader Chrome extension: two Manifest V3 architectural challenges and their fixes
Dev.to
The Push Notification Bug That Took Three Layers to Find
Dev.to
How MV3 Service Workers Made Me Use an Offscreen Document Just to Play a Goat Sound
Dev.to
Optimizing Network Interception in Manifest V3: Inside the Architecture of an Asynchronous Blocklist Extension
Dev.to