Create a proprietary scheme for loading web-accessible resources.

content/public/common/url_constants.h

Index: content/public/common/url_constants.h
diff --git a/content/public/common/url_constants.h b/content/public/common/url_constants.h
index d04328d8c492b54f16c2ae9542c9cd935b837252..a9eec3310fd8eb3f174677a20bfe59e00f98d67f 100644
--- a/content/public/common/url_constants.h
+++ b/content/public/common/url_constants.h
@@ -19,6 +19,7 @@ CONTENT_EXPORT extern const char kChromeDevToolsScheme[];
 CONTENT_EXPORT extern const char kChromeUIScheme[];  // Used for WebUIs.
 CONTENT_EXPORT extern const char kGuestScheme[];
 CONTENT_EXPORT extern const char kMetadataScheme[];
+CONTENT_EXPORT extern const char kResourceScheme[];

[Mike West, 2014/11/18 20:38:51]

Can we name this something less generic? I'd like to narrowly scope the scheme
to blink-in-js; `private-script-resources`, `blink-in-js-resources`,
`resources-that-we-wish-you-wouldn-t-block-via-csp-resources`, etc. Something
snappy. ;)

[jbroman, 2014/11/18 20:47:18]

It's not tied to Blink-in-JS (Blink-in-JS is more likely to need to load things
this way, but it's entirely reasonable to write the controlling code in C++ but
still want to express your style in CSS, getting device-scale-factor image
loading support, :hover support, media queries, etc. for free).

Some random alternatives (though the "chrome-" prefix is nice insofar as its
clear it's vendor-specific).

kPrivateResourceScheme = private-resource:// or chrome-private-resource://
kInternalResourceScheme = internal-resource:// or chrome-internal-resource://

(with corresponding file renames, probably)

I can bikeshed more over IM if you wish. :)

 CONTENT_EXPORT extern const char kSwappedOutScheme[];
 CONTENT_EXPORT extern const char kViewSourceScheme[];
 #if defined(OS_CHROMEOS)