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

F2F: This is no longer a problem as we aren't going to expose reserved clients. If a client is navigated while it's navigating, it should behave like iframes do in the same situation. I assume that the latest navigation happens and the old aborts, as long as the new client hasn't been created yet.

Use case: You serve something online-first, but it gets stuck after headers & some body. You want to start again, switching to an offline-first model. Client navigation gets you this.

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