Re: [w3c/ServiceWorker] Making a concurrent request for navigations (#920)

More specific feedback: Chrome's initial implementation will reject enable()/disable() if there is no active worker. We could change behavior later to allow it but it'd make the implementation a bit more complex. Related is https://github.com/w3c/push-api/issues/221, the push spec's subscribe() waits for an active worker but this can cause a deadlock (neither implementation currently follows this: Chrome rejects if no active worker and Firefox resolves without waiting).

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