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

mkruisselbrink left a comment (w3c/manifest#1208)

I'm curious about "APIs do this all the time to fix bad practices etc - using new features requires fixing issues", do you have examples of this? 
The main thing I can think of is requiring secure contexts for new features, but as far as I know even for that case there isn't consensus that it is the right tradeoff.

On the other hand, it is easier to launch a new feature with an "id" requirement and then later relax that requirement than going the other way around, even if technically nothing in the new feature truly requires an explicit id.


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

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