Re: [slightlyoff/ServiceWorker] Eliminating SW startup latency for common case (#920)

Again I think this is scenario-solving to the extreme. I'd rather look at solutions that solve this issue for Facebook, but maybe some other sites too.

We already have `<link rel="preload">` for preloading and we should lean on its semantics as much as possible. The missing part is a way to assign preloads to a navigation request before spinning up the service worker.

`<link rel="preload">` already needs to define the life of its cache & how requests are matched to it, so I don't see why we should reinvent that.

The preloaded URL may be the same across every navigation on Facebook's origin, but I don't think that will be generally true.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/920#issuecomment-233863954