Add scheme exceptions for isSecureContext

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

 // 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) {
   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 })
 });