Open Bug 1283054 Opened 4 years ago Updated 10 months ago
Measure impact of e10s-multi on service-worker-backed navigation
From https://github.com/slightlyoff/ServiceWorker/issues/920 it seems allocating a new content process and routing the navigation request through there can be expensive for Chrome. If that is the case for our setup as well, that would be problematic.
We have to implement our new service worker e10s changes first. What we have now won't work correctly for multi-e10s.
Depends on: ServiceWorkers-e10s
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.