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

>We'd rather not have to spin up an SVG renderer alongside the HTML renderer.

@mgiuca  Oh, didn't think of that. Makes sense in that respect. The reason I mentioned SVG is because of good scaling while still providing for richness in graphics and animation, contained in one .svg file.

>plus it would be a barrier to entry for devs to have to supply separate SVG along with their HTML page.

Perhaps it won't be if its made optional. Default could be current way, and if someone wants more richness in the splash screen, then they could opt for this way.  

>full HTML page for the splash screen

What if a person had embedded or inline svg in that html page? SVG renderer might then be needed anyway in that case? 

>The avenue we are pursuing is to have a full HTML page for the splash screen, but the UA takes a screen grab of the page at install time (or perhaps first load).

I think first load would make more sense than install time. A user could be at any page during install time. Wouldn't be good to capture that. First load might be better there. 

Also, by screen grab, are you talking something like a DOM snapshot of the page? Or an actual snapshot like a png? I'm assuming the former. 

👍 to thinking more about this area. There is some room for improvement here. 

-- 
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-312532620