Trigger Dangerous indicator for unsafe subresources

chrome/browser/safe_browsing/ui_manager.cc

Index: chrome/browser/safe_browsing/ui_manager.cc
diff --git a/chrome/browser/safe_browsing/ui_manager.cc b/chrome/browser/safe_browsing/ui_manager.cc
index 08bff13331e033003506e206a2baa59b9545ddb3..6cdc91586cff1ea2f834bfce8828ab1337c72777 100644
--- a/chrome/browser/safe_browsing/ui_manager.cc
+++ b/chrome/browser/safe_browsing/ui_manager.cc
@@ -389,6 +389,9 @@ void SafeBrowsingUIManager::AddToWhitelistUrlSet(const UnsafeResource& resource,
   } else {
     site_list->Insert(whitelisted_url);
   }
+
+  // Notify security UI that security state has changed.
+  web_contents->DidChangeVisibleSecurityState();

[Nathan Parker, 2016/10/27 18:49:32]

Could this go in the "{Insert(whitelisted_url)..}" block so it doesn't trigger
an unnecessary change when the user clicks through (assuming that's correct)? 
It'd just be an optimization, so maybe simpler not to.

[estark, 2016/10/27 20:06:09]

I could be convinced either way, but I lean slightly towards leaving it as-is,
on the grounds that this class shouldn't be selective about what state changes
are interesting to the omnibox security indicator. For example, hypothetically
we could want to use a different icon for pending vs whitelisted urls, or
something like that.

 }
 
 bool SafeBrowsingUIManager::IsWhitelisted(const UnsafeResource& resource) {