- From: Matt Giuca <notifications@github.com>
- Date: Sun, 28 Jun 2020 21:17:41 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 29 June 2020 04:17:55 UTC
I believe [`ManifestImageResource.platform`](https://www.w3.org/TR/appmanifest/#platform-member) should be considered at risk. I don't think Chrome implements it ([`ParseIcons`](https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/modules/manifest/manifest_parser.cc;l=387;drc=730040c92ecd7b32a67faa689133d3074e149157;bpv=1;bpt=1) in Chrome's manifest parser doesn't look at the `"platform"` member). And I don't think it's necessary. Does Gecko or WebKit implement this? Since we added `maskable` and `monochrome`, we're trending towards specifying purposes with specialized semantics, but not specific to any OS. I think that's much better than letting developers supply specific icons for each OS. I think it can be removed. -- 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/issues/909
Received on Monday, 29 June 2020 04:17:55 UTC