Re: [w3c/manifest] Allow setting an HTTP request for server side PWA detection (#954)

> Looping back here, it looks like we can solve the first request problem with the Critical-CH header:
> https://github.com/WICG/client-hints-infrastructure/blob/master/reliability.md#critical-ch
> 
> So I think this should solve this?

An I reading it correctly that the client would get back the `Critical-CH` header and then pause the loading/rendering prices while it re-requests all of the resources? If so, what is the performance impact on slow networks? It seems like it would cause double downloads of at least the HTML. Does the engine stop all additional asset requests when it gets this back? How does this play with HTTP2 if the server is pushing files into the stream with a request?

-- 
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/manifest/issues/954#issuecomment-786753398