-
Notifications
You must be signed in to change notification settings - Fork 388
Relax top-level service worker requirement #147
Comments
This is very exciting :) On Fri, 29 Jul 2016, 11:43 Jeffrey Posnick, [email protected]
|
👍 . @jeffposnick I wasn't able to locate a Chromium bug on the related ServiceWorker thread to track when we might be able to switch to the ideas in #43. Do you know if one has been filed yet? |
I haven't seen one. I'll ask around internally to make sure it's on the Chrome engineering team's radar. |
The pre-requisite functionality is tracked in Chrome at https://bugs.chromium.org/p/chromium/issues/detail?id=648295 |
Developers who need this functionality are encouraged to migrate to https://workboxjs.org/ That has superseded any plans to rewrite |
As per w3c/ServiceWorker#839 (comment), it sounds like the service worker specification will be updated to allow any byte-by-byte changes to
importScripts()
resources to trigger the Install flow. This opens the door towards allowing developers to pull insw-precache
's output viaimportScripts()
instead of forcing them to use it as their top-level service worker.It also might open the door to some of the refactoring that @gauntface has advocated for in #43 and elsewhere.
This all will depend on browsers shipping service worker implementations that adhere to the new behavior, so this issue is more of a long-term reminder than anything immediately actionable.
CC: @addyosmani @wibblymat
The text was updated successfully, but these errors were encountered: