- From: Aaron Gustafson <notifications@github.com>
- Date: Wed, 11 Dec 2019 11:48:25 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 11 December 2019 19:48:27 UTC
aarongustafson commented on this pull request. > + When processing a <a>monochrome</a> icon, the user agent MUST NOT use + the red component, green component, or blue component of a pixel. If + it has alpha equal to zero, the user agent SHOULD NOT display it. + If it the alpha component is greater than zero, the user agent SHOULD + display it with any tint. + </p> + <p> + If no monochrome icon is defined when an icon with a solid icon must + be presented, the user agent MAY show a fallback icon. + </p> + <p class="note"> + Designers of <a>monochrome</a> icons are recommended to set all + pixels to black and use transparency to create a silhouette of their + icon. + </p> + <p> Github assigned the comment to a line, which made this slightly confusing. I was not saying this was for authors, but rather for implementors to give them the flexibility to adapt the icon as necessary. -- 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#discussion_r356800075
Received on Wednesday, 11 December 2019 19:48:27 UTC