Index: chrome/browser/themes/theme_service.cc |
diff --git a/chrome/browser/themes/theme_service.cc b/chrome/browser/themes/theme_service.cc |
index 8ce03c189ad2afd728937327d47a269f88cf7db0..275c37eed4dc96cc24fad918fe71ce194d63d394 100644 |
--- a/chrome/browser/themes/theme_service.cc |
+++ b/chrome/browser/themes/theme_service.cc |
@@ -495,7 +495,8 @@ SkColor ThemeService::GetDefaultColor(int id, bool incognito) const { |
#endif |
} |
- return ThemeProperties::GetDefaultColor(id, incognito); |
+ // Always fall back to the non-incognito color when there's a custom theme. |
+ return ThemeProperties::GetDefaultColor(id, incognito && !theme_supplier_); |
Peter Kasting
2016/03/18 20:53:50
Hmm. Couldn't this also break some themes, if we
Evan Stade
2016/03/18 21:15:21
Perhaps, but I checked about 8 themes and the only
Peter Kasting
2016/03/18 21:22:53
No; instead I think we should only disable |use_in
|
} |
color_utils::HSL ThemeService::GetTint(int id, bool incognito) const { |
@@ -505,7 +506,8 @@ color_utils::HSL ThemeService::GetTint(int id, bool incognito) const { |
if (theme_supplier_ && theme_supplier_->GetTint(id, &hsl)) |
return hsl; |
- return ThemeProperties::GetDefaultTint(id, incognito); |
+ // Always fall back to the non-incognito tint when there's a custom theme. |
+ return ThemeProperties::GetDefaultTint(id, incognito && !theme_supplier_); |
} |
void ThemeService::ClearAllThemeData() { |