Implement '[SecureContext]' IDL attribute for interfaces, methods and attributes.

third_party/WebKit/Source/bindings/tests/idls/core/TestInterfaceSecureContext.idl

Index: third_party/WebKit/Source/bindings/tests/idls/core/TestInterfaceSecureContext.idl
diff --git a/third_party/WebKit/Source/bindings/tests/idls/core/TestInterfaceSecureContext.idl b/third_party/WebKit/Source/bindings/tests/idls/core/TestInterfaceSecureContext.idl
new file mode 100644
index 0000000000000000000000000000000000000000..8ca46d1936fe78d934560d11fc32add61d92efef
--- /dev/null
+++ b/third_party/WebKit/Source/bindings/tests/idls/core/TestInterfaceSecureContext.idl
@@ -0,0 +1,19 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+[Exposed=(Window,Worker)]
+interface TestInterfaceSecureContext {

[haraken, 2016/08/04 13:51:17]

Instead of adding a new IDL file, can we add these attributes/methods to
existing IDL files? I don't want to bloat # of files in bindings/test/results/
:)

[Mike West, 2016/08/04 17:38:15]

Is there really a cost to more test result files? It seems simplest to have
small tests that verify a certain type of behavior, rather than adding 12
attributes to an unrelated interface.

I actually split these out of `TestInterface.idl` because it had
`RuntimeEnabled` on the interface itself, which really confused me when I was
trying to determine if the results were correct (as it changed the generated
code).

I'll defer to y'all on this, but I'd prefer to keep this distinct.

[bashi, 2016/08/04 23:16:13]

Don't we need to have a test for an interface which has [SecureContext]  anyway?

[SecureContext]
interface TestInterfaceSecureContext2 {
 ...
}

[haraken, 2016/08/05 04:05:38]

Yeah, good point. So shall we add:

- these attributes/operations to an existing test IDL file
- a new IDL file for an interface with [SecureContext]

?

mkwst@: In general, I prefer not bloating # of testing IDL files because it
unnecessarily increases the CL size of changes to the IDL compiler.

[Mike West, 2016/08/05 07:42:47]

Done.

+    [SecureContext] void secureContextMethod();
+    [SecureContext] attribute bool secureContextAttribute;
+    [SecureContext,RuntimeEnabled=SecureFeature] void secureContextRuntimeEnabledMethod();
+    [SecureContext,RuntimeEnabled=SecureFeature] attribute bool secureContextRuntimeEnabledAttribute;
+    [SecureContext,Exposed=Window] void secureContextWindowExposedMethod();
+    [SecureContext,Exposed=Window] attribute bool secureContextWindowExposedAttribute;
+    [SecureContext,Exposed=Worker] void secureContextWorkerExposedMethod();
+    [SecureContext,Exposed=Worker] attribute bool secureContextWorkerExposedAttribute;
+    [SecureContext,Exposed=Window,RuntimeEnabled=SecureFeature] void secureContextWindowExposedRuntimeEnabledMethod();
+    [SecureContext,Exposed=Window,RuntimeEnabled=SecureFeature] attribute bool secureContextWindowExposedRuntimeEnabledAttribute;
+    [SecureContext,Exposed=Worker,RuntimeEnabled=SecureFeature] void secureContextWorkerExposedRuntimeEnabledMethod();
+    [SecureContext,Exposed=Worker,RuntimeEnabled=SecureFeature] attribute bool secureContextWorkerExposedRuntimeEnabledAttribute;
+};