- From: Peter Beverloo <notifications@github.com>
- Date: Wed, 25 Sep 2019 08:29:02 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 September 2019 15:29:25 UTC
I'm all for being specific, but it should be clear that we're going to run into situations where _(a)_ the appropriate (modifyable) icon hasn't been provided by the developer, or _(b)_ the user's device expects something different from what the browser has selected on the developer's behalf, unbeknown to the browser. As Christian wrote, iOS wants maskable icons. Windows wants coloured icons. On Android, for most default launchers, it depends on what the icon _describes_: photos and logos should be full colour, whereas icons should be masked in the app's theme colour. Considering further variables such as colour scheme (e.g. dark mode), differences between OS versions, and so on, the number of permutations of icons we'd ask developers to provide is unreasonable. Having a purpose that comes down to "do whatever needs doing" can be the starting point for a simple implementation. Being able to specify multiple icons with more specific purposes is a good second step. Perhaps more controversial, but I also think we should consider enabling developers to provide specific resources if they feel the specialization is justified. -- 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/795#issuecomment-535078048
Received on Wednesday, 25 September 2019 15:29:25 UTC