Re: [w3c/manifest] Some questions and points about the images in the current spec (#744)

> splash_screens

There has never been a `splash_screens` member, nor have any browsers (that I know of) ever implemented such a thing.

Chrome makes its own splash screens by generating them from icons, but this a UI feature of one browser. Chrome documents it in the link you supplied; we don't document browser-specific UI in the manifest spec. I don't think it's appropriate to codify this in the spec.

Do not confuse this with `screenshots`. Those are completely unrelated (you wouldn't want a splash screen image to show up in a store as a screenshot, or vice versa).

> Icons

The idea is that you supply icons of any size you want, and the user agent picks the ones it wants to use. Some browsers (like Chrome) specify icons they expect, but that doesn't need to be codified in the spec. Doing so would unnecessarily limit us from expanding the set of icons in the future.

I don't think Chrome has requirements of any specific icon size. To install an app, it requires some minimum (I think 144) but that is a proprietary installation requirement, not a requirement for processing the manifest.

> screenshots

Similar to icons, you should just supply whatever sizes you want, and storefronts will pick the ones they want to display.

I don't actually know of any processors that use the `screenshots` tag (maybe the Microsoft Store?)

> density

Where is that `splash_screens` example from? I don't think this has ever been specced or implemented, but it may have been discussed somewhere.

> Draft Date

It's true. Something we discussed at W3C TPAC in October is bringing this spec to a more stable place, like a W3C Candidate Recommendation. It's changed a lot when basically only Chrome was implementing. Now that we have essentially 4 major implementations, it is a lot harder to change, so you should expect to see a lot less breakage in the future.

Hope this answers the questions. Closing the issue since this isn't actionable.

-- 
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/744#issuecomment-443608490