Settings icon is not visible on Chrome OS in extension with contrasting foreground/background tab colors |
|||||
Issue descriptionChrome Version: Chrome 59.0,3065,0 OS: Chrome OS Device: Chromebook Pixel 1 What steps will reproduce the problem? (1) Install https://chrome.google.com/webstore/detail/grass/mmiboiefncpfjihjdedpaoammipkilla?hl=en (2) Open chrome://settings (3) Open a new tab What is the expected result? The chrome://settings icon stays visible on in the tab strip. What happens instead? The chrome://settings icon is not visible. I'm guessing that there is logic to turn the Settings icon white because the foreground tab strip tab color for the theme is dark (green). However, the background tab color is white, where this is not visible. I can only reproduce with this theme on Chrome OS. - With the same theme on macOS, the icon is gray for fg and bg tabs. - With a different theme on Chrome OS, the icon is also gray for fg and bg tabs.
,
Apr 28 2017
This might be fixable, but I'm not sure how much I'd prioritize it. If we don't colorize like this it's quite possible for the icon to be invisible on either a fg or bg tab, e.g. on Mac if you install a grey theme the icon will be invisible. I think Views is overall in a better place than Mac here, even if not perfect.
,
Apr 28 2017
Agreed. a) Settings opens in its own window by default on Chrome OS. b) The problem doesn't seem unique to settings? Any icon with a similar color scheme would have the same problem, wouldn't it? estade@ - you seem to know more about this than I do? Putting this on your plate unless you think there is something Settings specific you think we should do.
,
Apr 28 2017
Correct, it's not specific to settings. I'm not going to be working on it any time soon, though I can help answer questions if anyone takes it up. (I think priority 3 is appropriate.)
,
Apr 28 2017
,
Apr 30 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xiy...@chromium.org
, Apr 28 2017Owner: steve...@chromium.org
Status: Assigned (was: Untriaged)