Material top chrome mode: toolbar icon size is 16px instead of 19px
Reported by
woxxom@gmail.com,
May 18 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2739.0 Safari/537.36 Steps to reproduce the problem: 1. Use the default setting for chrome://flags/#top-chrome-md (it's "enabled" as of the specified Chrome dev build) What is the expected behavior? Toolbar icon size should be 19x19px (or 38x38px on retina displays) as per documentation What went wrong? Toolbar icon size is 16px, so small details are distorted/blurry for all extensions that correctly provide 19/38px toolbar icon. Did this work before? Yes Before the chrome://flags/#top-chrome-md flag was enabled by default on Dev channel Chrome version: 52.0.2739.0 Channel: dev OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 Screenshot: https://i.imgur.com/5TkBBIC.png
,
May 30 2016
Can confirm on: 1. Linux stable(!) Version 51.0.2704.63 (64-bit) / Ubuntu 14.04 (no flags) 2. Windows Version 53.0.2751.0 canary (64-bit) / Windows 10 (no flags) 3. Windows Version 51.0.2704.63 m / Windows 10 High-DPI (with flag enabled) The major problem is that it spilled into Linux stable, and setting the flag to Non-Material has no effect.
,
May 30 2016
Regarding badges (and not icons themsleves): https://bugs.chromium.org/p/chromium/issues/detail?id=612748
,
Jun 9 2016
This is a planned change. crbug.com/546206
,
Jun 12 2016
This change made the icons less legible: 1. a lot of extensions won't be updated to have a 16px icon so a distorted scaled-down version will be displayed. 2. a 16x16px icon is too small, there's too little space to include nicely drawn details so many icons will look alike. 3. since the icons are small and the overlayed infobadges cover parts of the icon there will be many users who have similar looking icons, so they'll have to examine carefully before clicking the one they need, losing their time due to bad design. Whoever pushed this change didn't think it through or had faulty reasoning (probably something ludicrous from a user point of view like "simplifying of codebase" or "simplifying requirements for extensions").
,
Jun 12 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by woxxom@gmail.com
, May 18 2016