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
Sry, forget my initial post, my configuration was somehow messed up. But while testing and digging into serviceworkers I discovered some other issues with the ServiceWorkerManager that I don't understand.
When reloading the page a servicworker that is waiting to be activated is ignored cause onupdatefound is not triggered in this case.
Does calling onNewServiceWorkerFound with registration.waiting make sense? At that point there should usually be either no waiting SW or an older one that is to be replaced with the new one that triggered the onupdatefound event. IMHO the way it is at the moment onupdatefound will always be called together with onInstalling what is unnecessary.
I think using onupdatefound like it was until v2.2 (just calling it once on setup if registration.waiting is true) would make more sense and would solve problem nr. 1.
The text was updated successfully, but these errors were encountered:
Sry, forget my initial post, my configuration was somehow messed up. But while testing and digging into serviceworkers I discovered some other issues with the ServiceWorkerManager that I don't understand.
I think using onupdatefound like it was until v2.2 (just calling it once on setup if registration.waiting is true) would make more sense and would solve problem nr. 1.
The text was updated successfully, but these errors were encountered: