Re: [w3c/manifest] Why is purpose a "unordered set of unique space-separated tokens"? (#903)

I suspect this probably inherited from an `ImageResource`’s `sizes` member as well.

I guess the main question I have is: What benefit would we gain from this moving to being an array instead of a space-separated string, especially considering that we’d need to maintain the string parser for legacy compat reasons?

It might be the more "correct" way to do it, but it would also be more verbose (brackets, commas, more quotes). The only benefit I see is that it could enable us to have `purpose` values that contain a space, but it seems like we can work around that relatively easily. Personally I think we should just keep it as-is. We already need the string parsing for `sizes` anyway.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/903#issuecomment-1029292148

You are receiving this because you are subscribed to this thread.

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