[Mac][Material Design] Adjust EV chip to match Material Design spec.

chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm

Index: chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm
diff --git a/chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm b/chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm
index 22d28186f262b1e28fc14d42ed9b9de3cf6fb527..8ea6b87d119e86fb0a8d5acbf8de383fa14c3f85 100644
--- a/chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm
+++ b/chrome/browser/ui/cocoa/location_bar/location_bar_view_mac.mm
@@ -559,10 +559,11 @@ void LocationBarViewMac::UpdateLocationIcon() {
 
   SkColor vectorIconColor = gfx::kPlaceholderColor;
   gfx::VectorIconId vectorIconId = gfx::VectorIconId::VECTOR_ICON_NONE;
-  const int kIconSize = 16;
+  int iconSize = 16;

[tapted, 2016/04/22 00:41:52]

these should all be hacker_style

const int kDefaultVectorLocationIconSize = 16;
const int kEVBubbleVectorLocationIconSize = 12;

int icon_size = kDefaultLocationIconSize; etc


(inDarkMode should be hacker_style too.. `const bool kInDarkMode` is another
option, but the style guide is a bit vague about whether things declared `const`
that are not *compile time* const, should be kFooSyle or just remain
hacker_style)

[shrike, 2016/04/22 05:46:30]

By "hacker_style" you mean with underbars? This is an ObjectiveC file, and the
convention is camel case? I;m not sure what part of the style guide you are
thinking of.

[tapted, 2016/04/22 06:09:48]

yup - underbars. And the naming scheme for Objective-C isn't based on the file
extension, but on whether it's in an Objective C class, which is easiest to
apply as "any new declarations between @{imlementation,interface,etc.}/@end.
E.g. `web_contents` appears in this file quite a bit, and all the methods take
parameters in hacker_style.

go/cppguide?cl=head#Constant_Names says "Variables declared constexpr or const,
**and whose value is fixed for the duration of the program**, are named with a
leading "k" followed by mixed case."

(i.e. I interpret that as meaning if something is declared `const` but
initialized by a (non-constexpr) method call, then it should not have
kNamingStyle)

[shrike, 2016/04/22 06:24:15]

Ah, OK, I see where I was confused. Thanks.

   if (ShouldShowEVBubble()) {

[tapted, 2016/04/22 00:41:52]

Hm. could this even move into ev_bubble_decoration.mm? It looks like
ev_bubble_decoration_ is either visible or not, but it always has the same
"valid" icon -- there shouldn't ever be a need to call SetImage on it after
construction.

[shrike, 2016/04/22 05:46:30]

In general the icon does not change but that's not always true (if, for example,
you have an Incognito window that has it start of in dark mode and then you
change the theme to a "light" custom theme).

[tapted, 2016/04/22 06:09:48]

wouldn't that need handling for `vectorIconColor` on line 565 to take into
account in_dark_mode

[shrike, 2016/04/22 06:24:15]

The vector icon code is a little screwy (if you ask me). It always takes a
color, but sometimes the color is ignored. In the case of the lock, when you're
in dark mode the color is hard-coded within the icon to be white.

[tapted, 2016/04/25 21:48:10]

Acknowledged.

     vectorIconId = gfx::VectorIconId::LOCATION_BAR_HTTPS_VALID_IN_CHIP;
     vectorIconColor = gfx::kGoogleGreen700;
+    iconSize = 12;
   } else {
     vectorIconId = omnibox_view_->GetVectorIcon(inDarkMode);
     if (inDarkMode) {
@@ -577,7 +578,7 @@ void LocationBarViewMac::UpdateLocationIcon() {
 
   DCHECK(vectorIconId != gfx::VectorIconId::VECTOR_ICON_NONE);
   NSImage* image = NSImageFromImageSkia(gfx::CreateVectorIcon(
-      vectorIconId, kIconSize, vectorIconColor));
+      vectorIconId, iconSize, vectorIconColor));
 
   location_icon_decoration_->SetImage(image);
   ev_bubble_decoration_->SetImage(image);