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

F2F:

* WebKit & MS think the preflight is a good idea
* Not keen on the "preflight" naming
* We need to name this, but not now
* It's for GET navigation
* The request the same as `event.request` plus a dict with an addHeaders property, allowing the setting of headers & the change of mode - but this is tricky when mode is navigate, which it is
* It happens for everything in scope
* This API should sit on the registration object
* It should return a promise, which resolves once the rule is in place, or rejects if the options are invalid (not-allowed headers)
* Once the rule is in place, the preflight will always be done, it's not optional from the browser's point of view, for consistency it should be done for every GET navigate
* We can add url prefix in later
* concurrentFetch?


---
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-236251448