Re: [w3c/manifest] Add a unique identifier for a PWA (#586)

I think Chrome desktop is going to be the main pain point here, since that's the one that doesn't use manifest URL. If @dmurph and @alancutter are happy with migrating Chrome desktop over to manifest, I think we'll all be in a much better place (and yes, we can live with that and add `id` field later if there are still issues).

FWIW, the issue with just having manifest as the ID and not an explicit `id` field is that it restricts what people are able to do with their site layout. Even if developers are no longer having \*this\* issue due to versioning their manifest URL, there is a reason developers like to version assets (for caching), so forcing them to not version their manifest URL could be causing other problems that we don't have much visibility into. That is why I originally proposed the `id` field.

-- 
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/586#issuecomment-674655524