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/content_scripts/background_page_iframe/background.js b/chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
similarity index 72%
copy from chrome/test/data/extensions/api_test/content_scripts/background_page_iframe/background.js
copy to chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
index 8da0bc66325d6a56011e02db6c9d9ab20a37cfc2..34715d9ff98f8db27a8c9f3f9a7c3e931cd5d1f9 100644
--- a/chrome/test/data/extensions/api_test/content_scripts/background_page_iframe/background.js
+++ b/chrome/test/data/extensions/api_test/webrtc_from_web_accessible_resource/test.js
@@ -4,8 +4,7 @@
 
 chrome.test.getConfig(function(config) {
   var iframe = document.createElement('iframe');

[robwu, 2015/10/08 21:25:18]

This variable seems unused, remove it.

And you could ditch this background page if you use the following:

// Right after ASSERT_TRUE(RunExtensionTest(...
ui_test_utils::NavigateToURL(browser(),
   embedded_test_server()->GetURL("/extensions/test_file.html"));

[jww, 2015/10/09 21:39:26]

I cleaned this up a bit, but it's now necessary for a different reason. A
comment explains it in the latest patch, but basically we need the background
page to 'pass' once to sort of kickstart the test, even though the true success
and failure are in the content script.

-  iframe.src =
+  var url =
       'http://a.com:' + config.testServer.port + '/extensions/test_file.html';
-  iframe.onload = function() { chrome.test.sendMessage('iframe loaded'); }
-  document.body.appendChild(iframe);
+  chrome.tabs.create({ 'url': url })
 });