[Password Generation] Update Aura UI

chrome/browser/ui/autofill/password_generation_popup_view.cc

Index: chrome/browser/ui/autofill/password_generation_popup_view.cc
diff --git a/chrome/browser/ui/autofill/password_generation_popup_view.cc b/chrome/browser/ui/autofill/password_generation_popup_view.cc
index e2e344f9efb3a197232f40af012628039a6284f5..12e0c7dfe4dfd26ac4d1560d3f46c57adf898b51 100644
--- a/chrome/browser/ui/autofill/password_generation_popup_view.cc
+++ b/chrome/browser/ui/autofill/password_generation_popup_view.cc
@@ -13,6 +13,6 @@ const SkColor PasswordGenerationPopupView::kExplanatoryTextColor =
 const SkColor PasswordGenerationPopupView::kDividerColor =
     SkColorSetRGB(0xE9, 0xE9, 0xE9);
 const SkColor PasswordGenerationPopupView::kLinkColor =

[Evan Stade, 2014/06/19 00:16:35]

I have a feeling these colors should either be deleted and replaced with values
from the native theme, or moved into the native theme. (Why is the link color
different here than elsewhere in chrome?)

[Garrett Casto, 2014/06/20 23:47:01]

Rebecca should hopefully be able to give a better answer here. I'm assuming that
Chrome is moving towards a different UI style but isn't going to change the
entire UI all at once.

FYI, it looks like the default is in ui::Link::GetDefaultEnabledColor(), not in
the theme for whatever reason. Your point obviously still stands.

[Evan Stade, 2014/06/23 18:20:40]

I think it would be good to make sure that assumption is correct. Hardcoded
values create inconsistencies and can break themes.
from native_theme.h:

    // TODO(benrg): move other hardcoded colors here.

-    SkColorSetRGB(0x55, 0x59, 0xFE);
+    SkColorSetRGB(0x55, 0x95, 0xFE);
 
 }  // namespace autofill