Update CM API IDL to use SecureContext

third_party/WebKit/Source/web/WebRuntimeFeatures.cpp

Index: third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
diff --git a/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp b/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
index ff366f0cfe9000647f4b38636d1102bb32c2e74c..edc86543901b34baa8114e66a46ae12dc858a4d6 100644
--- a/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
+++ b/third_party/WebKit/Source/web/WebRuntimeFeatures.cpp
@@ -298,10 +298,6 @@ void WebRuntimeFeatures::EnablePrintBrowser(bool enable) {
   RuntimeEnabledFeatures::setPrintBrowserEnabled(enable);
 }
 
-void WebRuntimeFeatures::EnableCredentialManagerAPI(bool enable) {
-  RuntimeEnabledFeatures::setCredentialManagerEnabled(enable);

[jdoerrie, 2017/04/26 12:20:35]

Dropping the entry in RuntimeEnabledFeatures.json5 resulted in
setCredentialManagerEnabled not being generated anymore, which is why I had to
remove this method and also the corresponding line in runtime_features.cc.

Looking at Mike's CL enabling CM API by default also other files were changed:
http://crrev.com/1720403003
That CL's description states that the "feature flag can be removed after ~a
release", which did not seem to happen yet. Should I go ahead and remove this
flag also in this CL?

[vasilii, 2017/04/26 17:44:09]

yes.

-}
-
 void WebRuntimeFeatures::EnableV8IdleTasks(bool enable) {
   RuntimeEnabledFeatures::setV8IdleTasksEnabled(enable);
 }