Re: [w3c/manifest] Richer splash screen backgrounds (#589)

Thanks for feedback!

**@marcoscaceres, re: Feature-policy/security-model for splash screen pages**

I think we should add to the spec something along the lines of _“UA may restrict set of APIs available while rendering the splash_screen_url page”_. Unless you have specific ideas in mind, I would leave this to later consideration depending on what UAs will decide to do and what problems they might run into.

**@kenchris, re: How static screenshots of splash screen pages interplay with windows of different size on desktop.** 

My claim was not that all webapps can load almost instantaneously, only that if good practices are followed (SW cache etc.), the time to first paint can be negligible. Let me know if you think this generalization is too broad, I don’t have experience with WebAssembly for example. The goal of this proposal is only to display a site-controlled image before the first paint, which happens very quickly on desktop and makes usefulness of this feature questionable there. 

If however UA would like to show a _splash_screen_url_ in a desktop environment, it can render it from SW cache very quickly (presumably just HTML + CSS + fonts). There is no need for screenshotting, and therefore no problem with resizeable windows. If UA does that, there is an open question of when to transition from _splash_screen_url_ to the web content. It could happen on _onload_, but some developer controllable mechanism (#372) could be proposed. Event.waitUntil(...) comes to mind, but I would leave spec’ing this out to a party who is interested in implementing it - at this point in time we (Google) are not.

To sum up, I believe this proposal is compatible with further developments we could consider for desktop.

-- 
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/589#issuecomment-325273121