[w3c/manifest] Should new manifest features require an explicit ID to be present in the manifest in order to be parsed? (Issue #1208)

mkruisselbrink created an issue (w3c/manifest#1208)

The current [proposal](https://github.com/WICG/manifest-incubations/blob/gh-pages/pwa-migration-explainer.md) for a feature to allow a manifest to indicate it describes the new home/identity of an old app/manifest says that the new manifest fields we're proposing should only be parsed if the manifest also includes an explicit ID. There isn't really any technical reason why we would make this a requirement, the idea is more that this could be a carrot to try to get more developers to follow best practices of having an explicit ID.

The TAG expressed some concerns about this requirement, so I figured it's worth answering more generically what peoples thoughts are about requiring the presence of an explicit ID in order for a browser to parse a new manifest field. Is this a reasonable idea? Or a terrible one?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1208
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1208@github.com>