id (non-standard?) manifest field for 3.0 will possibly conflict with the id field that is currently being added

[dmurph]

We have been working on adding the id field to the manifest for a year or so now:

• Add id member to manifest w3c/manifest#988
• https://github.com/philloooo/pwa-unique-id/blob/main/explainer.md
• Specify how updates work w3c/manifest#446
• Add a unique identifier for a PWA w3c/manifest#586

Does the id field in 3.0 behave as proposed in the pull request? If so - awesome! Just wanted to confirm :)

If not - is is possible for us to align here?

[fabricedesre]

Hi Daniel!

Yes the intent is to use the id field per spec. We moved all the non standard properties under the b2g_features property instead for clarity.

[dmurph]

Awesome! Thank you! I think one difference from our original discussion is that we expect the 'computed id' to be a resolved URL, so comparisons between computed ids would be URL comparisons.