ServiceWorker network activity in DevTools

[Preston Pham]

Hello,

We've noticed that our MV3 extension's ServiceWorker has network activity that shows up in a tab's DevTools. Previously on MV2, the background script activity would only appear on the background DevTools.

Is it possible to have MV3 mimic this behavior? As in constrain our SW's network activity to the SW DevTools only?

The current behavior is not ideal for us because our SW interacts with our application server (graphql) and also use Datadog for logging/telemetry. These network entries are noise that are now visible to our technical users.

I've only seen a mention about service worker initiated/intercepted requests in What's New In DevTools (Chrome 74), but it's not ideal for us to suggest using a search filter like `-is:service-worker-initiated` 

Thanks

[woxxom]

It's one of the several inherent downsides of using a service worker in a chrome extension, there are arguably much worse ones, e.g. the inability to use the built-in workspaces (live-edit and hot-reload) in devtools. Given the fact that these may be impossible to fix with the current architecture of Chromium or devtools, I guess we'll have to suffer the consequences of this mistake for years if not decades.