Re: [w3c/manifest] BREAKING CHANGE: Replace "badge" with "monochrome" (#833)

I'm not sure I can say for sure that we're going to use this, but I'd like us to wherever it makes sense (e.g., in notifications).

We currently parse the badge purpose, but we don't seem to use it anywhere (it might be that we use it on our server). I need to confirm that it isn't going to break any sites if we stop parsing "badge".

If I can confirm that, then I would be happy to change our parser to parse "monochrome" instead. I can't commit to actually using it, but I don't think that should stop us landing this change (it'd be going from one unused-in-Chrome field to another, so the "two implementor" rule isn't being any more violated than it is now). Perhaps as a separate issue we would look at offloading it from the CR version of the spec if there aren't two implementations at that time, but I don't think it should stop this landing.

-- 
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/pull/833#issuecomment-645168056

Received on Wednesday, 17 June 2020 05:56:15 UTC