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

The error page issue is fixable by the browsers.  We just need to stash the reason for the NetworkError on an internal attribute that content can't see.  Then we can use the correct network error page if its passed back to a navigation respondWith().

I also feel that the perf issues should be fixable long term.

I guess I'm just worried about contorting the API for short term issues.  If the problems can't be fixed, we could also add a sync boolean getter later.

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