Last modified: 2014-09-10 05:18:31 UTC
Created attachment 13254 [details] screenshot of icon with blurry edges
High quality SVGs are uploaded to commons and linked from here https://www.mediawiki.org/wiki/Echo_(Notifications)/Feature_requirements#Icons_and_types Ping Nick W. with questions.
(In reply to comment #1) > High quality SVGs are uploaded to commons and linked from here > https://www.mediawiki.org/wiki/Echo_(Notifications)/ > Feature_requirements#Icons_and_types > > Ping Nick W. with questions. Thanks! I changed it from email just because it applies to all the notification icons. I'm also going to file a tracking bug for other icons that I know suffer from this issue.
The watch icon was pointed out a while back to sync with mobile, but it still hasn't been fixed, super ugly on desktop, can't find the bug, Quim might want to do these as GSoC tasks since they're quick and uncontroversial.
@Design: We do still need an update or replacement for * the "welcome (elsewhere)" icon (all projects that aren't WikiPedia) * the "default/fallback" (for non-WMF sites that use the extension) Afaik, the rest of the "proposed" column are all approved by design and PM (I think Fabrice?), and ready to be switched. We just need a Product Manager to approve an engineer spending time actually implementing the switch.
Nick, thats why I mentioned Quim, I don't know that these changes are priority for any team, Echo is Maryana (Core features) not Fabrice, but Flow it priority for that team, so perhaps a community member or GSoC student can do all of these but the two you mentioned in question.
(In reply to comment #3) > The watch icon was pointed out a while back to sync with mobile, but it still > hasn't been fixed, super ugly on desktop, can't find the bug See Bug 35335 - Vector: Add SVG version of the watch star icon Bug 54307 - Watchlist icon on does not match on desktop and mobile skin Note: Google Code-in 2014 (the program of the many little tasks) was completed a few weeks back, and the next edition will start presumably on November. Google Summer of Code (the program if the few bigger projects) is not suitable for a task like this. Still, I just added the EASY keyword to iincrease its chances to be spotted by new contributors. (In reply to comment #5) > I don't know that these changes are priority for any team Then the priority of this bug should be low instead of high (or at least normal), since this field aims to simply reflect the current priorities.
