You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this time, ServiceWorker simply ignores the very first page that registers it. It should take control over this page right after it is activated. It doesn't make sense to ignore requests fetched after ServiceWorker is ready to work.
I think it's best to activate ServiceWorker before all. In order to achieve that, it should be able to be registered via http headers instead of Javascript.
The text was updated successfully, but these errors were encountered:
Blocking the page would create a huge drop in performance, as your first render is gated on everything in the install step. Instead, we're encouraging a more progressive (and faster) model.
If you must, you could serve a loading page from the server, then refresh it once the service worker installs. But again, this creates a much slower user experience so we don't recommend it.
At this time, ServiceWorker simply ignores the very first page that registers it. It should take control over this page right after it is activated. It doesn't make sense to ignore requests fetched after ServiceWorker is ready to work.
I think it's best to activate ServiceWorker before all. In order to achieve that, it should be able to be registered via http headers instead of Javascript.
The text was updated successfully, but these errors were encountered: