Re: [w3c/manifest] Allow app to load in parallel to splash screen (#559)

Hi Ashley,

The implementation in Chrome actually does load the URL at the same time that the splashscreen is being shown (this is the whole purpose of the splashscreen).

Importantly, the splashscreen hides on the first visually non-empty paint on the page, or when the page load event fires (which ever happens first). The non-empty paint happens first about 70% of the time, so this is probably why it seems like the URL is loading after the splashscreen disappears: the page still has stuff to be painted.

The first visual paint is really the most reliable signal we have that the page is doing something the user can see (the load event can be delayed if any non-dynamically specified resource on the page stalls). Have you looked at trying to reorganise your loading pipeline so you do more work before content gets painted?

-- 
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/559#issuecomment-287657079