Re: [manifest] Manifest format should support some way of including a splash screen (#9)

A feel that we are going in circles with this discussion.
* We can't use a plain image because it would require cropping or image magics that we can't really rely on browsers to do;
 * Opening an HTML page would fire up new processes which will make the splash screen slowing down the application startup;
 * Making a snapshot of an HTML page will require static page but developers want to do progress bars and stuff - also, it come with the problem of the snapshot happening at the "wrong time";
 * Other solutions a freaking complex (9 images?!).

Can we instead expect UA to build a splash screen from the information already in the Manifest? The ```icons```, ```theme_color```, ```name``` or even ```short_name``` sound like good information to build a splash screen.

We could add in the Manifest a hint to ask the browser to show a splashscreen (though, I'm not entirely convinced) but then, I wonder, when do the splashscreen hides? The ```load``` event is late and unreliable. Other events like ```DOMContentLoaded``` might be too early. What does Cordova or Firefox OS do?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/9#issuecomment-82992598