New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 615130 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

New tab search icon is green (OSX Material)

Project Member Reported by lgar...@chromium.org, May 26 2016

Issue description

Chrome 53.0.2748.0 
OSX 10.11.5

What steps will reproduce the problem?
(1) Open a new tab and look at the magnifiying glass icon.

What is the expected output?
The icon is blue, black, or gray.

What do you see instead?
The icon is green (green.png).

The icon used to be gray (gray.png), and it is blue for custom search with Material design (blue.png). I presume the green icon is an accident.
 
green.png
4.6 KB View Download
blue.png
11.2 KB View Download
gray.png
4.4 KB View Download

Comment 1 by shrike@chromium.org, May 26 2016

Cc: shrike@chromium.org
Labels: ReleaseBlock-Stable M-52
Owner: spqc...@chromium.org
Just to make sure, the correct color should be kChromeIconGrey?

Comment 3 by shrike@chromium.org, May 26 2016

That is correct.
I'm currently investigating this and the issue is potentially lower level. 
For some reason the icon is being refreshed with a security level of NONE which gives it the gray color, and then refreshed with a security level of SECURE, which changes it into green. 

I'm not sure if that's the correct behavior, my best bet might be to debug and compare the security level on Windows, which I still need to set chromium up on.
For what it's worth, I believe the security level of the new tab page is expected to be SECURE. DevTools shows the URL as https://www.google.com/_/chrome/newtab
Labels: OS-Mac
Status: Fixed (was: Assigned)
I can no longer replicate this on Canary 53.0.2760.0. Perhaps someone fixed the security logic for NTP? Anyway, I'm going to check if this is still an issue on M52

Status: Available (was: Fixed)
This CL fixed it: https://codereview.chromium.org/2028933002
I'll see if we can merge it to M52
Have you confirmed that the bug occurs in M52? I'm not sure how to reproduce it in the beta.
The issue looks fixed on M52 and M53 to me.
(Or maybe M52 never had the problem.)
Status: Fixed (was: Available)
Just tried it out. That's strange, I used to be able to reproduce it on Chromium for M52. Anyway, since it's fixed, I'll just go ahead and close this bug

Sign in to add a comment