Manifest: At risk: ManifestImageResource.platform?
I believe ManifestImageResource.platform should be considered at risk. I don't think Chrome implements it (ParseIcons 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.
mgiuca
All 7 comments
It may make sense to move this, alongside screenshots, to the App Information spec. I'll check with the folks consuming those details for storefronts. It's probably an edge case, but there might be instances where folks want to offer alternate screenshots for desktop and mobile, for example.
aarongustafson
on 29 Jun 2020
checked, we don't implement it in Gecko either. I'd be ok to remove it. Safari doesn't implement any icon support, so probably ok there too.
marcoscaceres
on 30 Jun 2020
Has the icon support story at Apple changed at all with their “homescreen web apps"? I saw the announcement, but have not read up.
aarongustafson
on 30 Jun 2020
Has the icon support story at Apple changed at all with their “homescreen web apps"? I saw the announcement, but have not read up.
No changes in the current iOS 14 beta 1. Still doesn’t use the icons from the manifest. I test with “all” possible icon sizes: https://ios-a2hs-demo.glitch.me/.
tomayac
on 30 Jun 2020
thanks for confirming @tomayac!
marcoscaceres
on 30 Jun 2020
I think it can be removed.
I agree. Web developers should not have to deal with OS/platform differences, and maskable and monochrome are great ways for developers to adapt their icons to the platform. So it makes sense to remove the platform member from ManifestImageResource. đź‘Ť
Also, I support @aarongustafson’s idea to move the platform member to App Information/screenshots, as developers might want to show different screenshots not only for mobile and desktop but also for various storefronts/platforms (which may have special requirements for those screenshots).
christianliebel
on 30 Jun 2020
- Update JSON schema
christianliebel
on 6 Jul 2020
Related issues
tomayac
·
9Comments
frlinw
·
7Comments
christianliebel
·
6Comments
MehrdadKhnzd
·
3Comments
TorstenDittmann
·
5Comments
Most helpful comment
I agree. Web developers should not have to deal with OS/platform differences, and
maskableandmonochromeare great ways for developers to adapt their icons to the platform. So it makes sense to remove theplatformmember from ManifestImageResource. 👍Also, I support @aarongustafson’s idea to move the platform member to App Information/screenshots, as developers might want to show different screenshots not only for mobile and desktop but also for various storefronts/platforms (which may have special requirements for those screenshots).