Re: [manifest] A means to control how long a splash screen should remain on screen. (#372)

> I think we don't all have the same vision of what a splashscreen should be used for. IMO, the browser should show a splashscreen up to the point of the first paint so an API to control the splashscreen isn't really needed. After the first paint, the website is able to control what's being rendered.

This seems initially like a good idea (it's actually what's in the spec right now). However, if you look at how splash screens are used, this doesn't really match the requirements developers have (e.g., https://github.com/w3c/manifest/issues/372#issuecomment-97087751). However, there might be room for a compromise position: some may opt for first-paint, while others might want more control. Having the API affords developers control over removing the splashscreen on first paint or when *the developer* deems the application is ready.  


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