Allowing registering arbitrary schemes as supporting the fetch API.

Source/platform/weborigin/SchemeRegistry.h

Index: Source/platform/weborigin/SchemeRegistry.h
diff --git a/Source/platform/weborigin/SchemeRegistry.h b/Source/platform/weborigin/SchemeRegistry.h
index e85d2bbec88c2cfb7286074719622f4faf9349b4..ff56b0280c5fac4b5d93ff542aedf1726cb0df97 100644
--- a/Source/platform/weborigin/SchemeRegistry.h
+++ b/Source/platform/weborigin/SchemeRegistry.h
@@ -91,6 +91,10 @@ public:
     static void registerURLSchemeAsAllowingServiceWorkers(const String& scheme);
     static bool shouldTreatURLSchemeAsAllowingServiceWorkers(const String& scheme);
 
+    // Schemes that can register as supporting the Fetch API.

[tyoshino (SeeGerritForStatus), 2015/08/26 07:24:48]

how about

"Schemes that are treated as supporting the Fetch API."

if this comment is about schemes registered by this function.

If this comment is only about this function, how about

"Register schemes that should be treated as supporting the Fetch API."

[not at google - send to devlin, 2015/08/26 16:30:32]

Done. I'll go with the former, looks consistent with the other comments in the
file.

+    static void registerURLSchemeAsSupportingFetchAPI(const String& scheme);
+    static bool shouldTreatURLSchemeAsSupportingFetchAPI(const String& scheme);

[pdr., 2015/08/25 21:25:10]

Why is there no unregister?

[not at google - send to devlin, 2015/08/25 22:04:45]

No need for it in our use case, which is registering chrome-extension - that
isn't going to change. Note that the other scheme registration functions in this
file can't be unregistered either.

+
     // Allow resources from some schemes to load on a page, regardless of its
     // Content Security Policy.
     // This enum should be kept in sync with public/web/WebSecurityPolicy.h.