Re: [manifest] Manifest "splash_screens" with animated "any" size SVG

Domenic is right. The design of the splashscreen feature is to keep the
user experience smooth while Chrome loads its processes and get the
first bits to render on the screen.

-- Mounir

On Thu, 15 Oct 2015, at 20:14, Domenic Denicola wrote:
> I don’t know the details of the implementation at all, but I would
> imagine this would defeat the point. My guess as to why Chrome does
> things this way is to show something before they spin up an entire
> HTML/SVG/etc. rendering engine. During that time displaying an animated
> SVG is going to be impossible.
> 
> If you want an animated loading screen for your app, you should work on
> using techniques like service worker to make sure that the app is loaded
> as fast as possible from the cache API, and you can display your loading
> screen while you fetch fresh content from the network.
> 
> From: Binyamin [mailto:7raivis@inbox.lv]
> Sent: Thursday, October 15, 2015 15:08
> To: public-webapps@w3.org
> Cc: Mounir Lamouri <mounir@lamouri.fr>
> Subject: [manifest] Manifest "splash_screens" with animated "any" size
> SVG
> 
> בע"ה
> 
> Hi,
> 
> 
> Google recently has published icon support centered in splash screen in
> Chrome 47 requiring icon minimum size 196px,
> https://developers.google.com/web/updates/2015/10/splashscreen.
> 
> I propose instead "splash_screens" with animated SVG that could display
> loading process similarly to almost any this days Android/iOS-native apps
> like Skype, etc. Link to spec
> https://w3c.github.io/manifest/#splash_screens-member
> 
>     {
>         "src": "splashscreen.svg",
>         "sizes": "any"
>     }
> 
> 
> 
> Binyamin
>

Received on Friday, 16 October 2015 08:19:19 UTC