Re: [w3c/ServiceWorker] error handling for aborted streams feeding a navigation request (#1184)

I retested in FF58 and chrome 61.  I left them both up for 10+ minutes:

Chrome:
* No service worker iframe continues to stream without timeout
* Service worker iframe with server stream times out at 330 seconds
* Service worker iframe with js stream times out at 330 seconds

Firefox:
* No service worker iframe continues to stream without timeout
* Service worker iframe with server stream continues to stream without timeout
* Service worker iframe with js stream times out at 330 seconds

In both browsers the "timeout" leaves the iframe with partial data.

I guess maybe the original issue is moot since we are aligned now.

Do we care about the difference in the middle iframe?  I think the FF behavior is due to us bypassing the SW completely for the data copying in that case which means killing the SW doesn't have any effect.  That may change with out multi-process refactor (if the process is killed, etc.).

-- 
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/1184#issuecomment-341725452