[Service Worker Registration] Registered extension scheme to allow service workers

chrome/renderer/chrome_content_renderer_client.cc

Index: chrome/renderer/chrome_content_renderer_client.cc
diff --git a/chrome/renderer/chrome_content_renderer_client.cc b/chrome/renderer/chrome_content_renderer_client.cc
index f8779f4b223d93ee564b07599f45c2e96763e64f..5cf266ee26836e7b8a6a52c5d7009328e38cd7bd 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -501,6 +501,10 @@ void ChromeContentRendererClient::RenderThreadStarted() {
   WebSecurityPolicy::registerURLSchemeAsBypassingContentSecurityPolicy(
       extension_resource_scheme);
 
+  // chrome-extension: resources should be allowed to register a Service Worker.
+  WebSecurityPolicy::registerURLSchemeAsAllowingServiceWorkers(

[Devlin, 2015/06/30 22:01:15]

We can actually move this into the constructor of ExtensionsRendererClient,
which would be a bit cleaner (since it's an extension-specific thing).  We
should probably do the same with the ones above, but let's hold off on that for
now.

We should also start adding at least a basic test, and ensure that we get
ever-so-slightly farther than we did before. :)  Then, we can continue to
iterate on that test, and it can serve as a nice progress tracker, too.

+      extension_scheme);
+
 #if defined(OS_WIN)
   // Report if the renderer process has been patched by chrome_elf.
   // TODO(csharp): Remove once the renderer is no longer getting