Please sign in to comment.
fix(service-worker): send initialization signal from the application
The Service Worker contains a mechanism by which it will postMessage itself a signal to initialize its caches. Through this mechanism, initialization happens asynchronously while keeping the SW process alive. Unfortunately in Firefox, the SW does not have the ability to postMessage itself during the activation event. This prevents the above mechanism from working, and the SW initializes on the next fetch event, which is often too late. Therefore, this change has the application wait for SW changes and tells each new SW to initialize itself. This happens in addition to the self-signal that the SW attempts to send (as self-signaling is more reliable). That way even on browsers such as Firefox, initialization happens eagerly.
- Loading branch information...