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
I like that approach! But, as the linked article suggests...
Similarly, if your web app uses a framework that performs additional setup after the page has loaded, look for a framework-specific event that signals when that work is done.
... shouldn't this be done even after Ember has booted and the first render has happened (e.g. scheduled afterRender in an initializer)?
On the service-worker-registration.js
Delay registration until after the page has loaded, to ensure that our precaching requests don't degrade the first visit experience.
See https://developers.google.com/web/fundamentals/instant-and-offline/service-worker/registration they recommend doing this so...
The text was updated successfully, but these errors were encountered: