Adding <keygen> Content Setting (Blink)

chrome/renderer/content_settings_observer.cc

Index: chrome/renderer/content_settings_observer.cc
diff --git a/chrome/renderer/content_settings_observer.cc b/chrome/renderer/content_settings_observer.cc
index 1e00b6cb13b413fc408f4680a4760943f5e11a2a..150ce509d9e5d53ec759d8d0751e5d2105267015 100644
--- a/chrome/renderer/content_settings_observer.cc
+++ b/chrome/renderer/content_settings_observer.cc
@@ -593,6 +593,10 @@ bool ContentSettingsObserver::allowRunningInsecureContent(
   return true;
 }
 
+void ContentSettingsObserver::didUseKeygen() {
+  Send(new ChromeViewHostMsg_DidUseKeygen(routing_id()));

[jochen (gone - plz use gerrit), 2015/11/25 08:54:34]

i'd include the frame url here, so you can show what sites want to use keygen in
the UI. I'd also store it somewhere in tab specific content settings

[svaldez, 2015/11/25 14:56:55]

We're currently using the top-level origin for the content-setting, and we
already display that in the UI through ContentSettingImage/Bubble. 

+}
+
 void ContentSettingsObserver::didNotAllowPlugins() {
   DidBlockContentType(CONTENT_SETTINGS_TYPE_PLUGINS);
 }