Re: [w3c/ServiceWorker] WindowClient.navigate() behavior for reserved clients and in-flight navigations (#1123)

Over here I proposed rejecting with InvalidStateError:

https://github.com/w3c/ServiceWorker/issues/1034#issuecomment-280357895

I think implementing anything active like this on reserved clients could be difficult and racy.  One of the reasons we thought it was ok to add reserved clients was that it could be lightweight and effectively implemented by pre-allocating a UUID.  If we require this kind of cancellation behavior it gets a lot harder to implement IMO.

-- 
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/1123#issuecomment-294930116