Add chrome-user-script:// protocol

This is a step towards getting user scripts working in extensions. It's a bit
janky to use the form chrome-user-script://<script file>/ (with no path), but
GURL assumes that there is always a host, but path is optional, making this
approach simpler than alternatives.

Review URL: http://codereview.chromium.org/16592

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7759 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/browser/net/chrome_url_request_context.h b/chrome/browser/net/chrome_url_request_context.h
index 7cd95f1..9ddbd47 100644
--- a/chrome/browser/net/chrome_url_request_context.h
+++ b/chrome/browser/net/chrome_url_request_context.h
@@ -39,6 +39,11 @@ class ChromeURLRequestContext : public URLRequestContext,
   // Gets the path to the directory for the specified extension.
   FilePath GetPathForExtension(const std::string& id);
 
+  // Gets the path to the directory user scripts are stored in.
+  FilePath user_script_dir_path() const {
+    return user_script_dir_path_;
+  }
+
  private:
   // Private constructor, use the static factory methods instead. This is
   // expected to be called on the UI thread.
@@ -65,6 +70,9 @@ class ChromeURLRequestContext : public URLRequestContext,
   // construtor and updated when extensions changed.
   ExtensionPaths extension_paths_;
 
+  // Path to the directory user scripts are stored in.
+  FilePath user_script_dir_path_;
+
   scoped_ptr<SQLitePersistentCookieStore> cookie_db_;
   PrefService* prefs_;
   bool is_off_the_record_;