Add scheme exceptions for isSecureContext

chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js

Index: chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
diff --git a/chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js b/chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
new file mode 100644
index 0000000000000000000000000000000000000000..b5ed3f6f00f62a65ed545a961f1d5fe205267ee7
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
@@ -0,0 +1,9 @@
+// Copyright 2015 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.
+
+chrome.test.getConfig(function(config) {

[Devlin, 2015/10/14 15:24:45]

Do we really need this step at all?

[jww, 2015/10/15 18:19:41]

Well, we don't need the getConfig() (so I'm removing), but as the comment below
mentions, we do need this initial notifyPass() just to get the tests started.
This is a pattern that I've seen in a number of other tests.

[Devlin, 2015/10/15 18:34:11]

But why do we need this instead of just, say, LoadExtension()?  That should load
the extension, and even wait for associated views to load.

[jww, 2015/10/15 22:38:06]

Because I'm ignorant and don't understand how extension testing works ;-) I've
changed it to just use load extension.

+  // On first call, just pass so the test can continue. The real checks are in
+  // the content script.
+  chrome.test.notifyPass();
+});