Support chrome-extension:// scheme in URLPattern.

chrome/common/extensions/docs/static/webRequest.html

Index: chrome/common/extensions/docs/static/webRequest.html
diff --git a/chrome/common/extensions/docs/static/webRequest.html b/chrome/common/extensions/docs/static/webRequest.html
index 9d2b44dd023acadf295cd5ccacce8c802c1d371e..f391374c548e4bffffdc331f45fe5ceee3bff9e0 100644
--- a/chrome/common/extensions/docs/static/webRequest.html
+++ b/chrome/common/extensions/docs/static/webRequest.html
@@ -195,7 +195,9 @@ explicitly requested.</p>
 triggered in various dimensions:
 <dl>
   <dt>URLs</dt>
-  <dd>URL patterns like <code>*://www.google.com/foo*bar</code>.</dd>
+  <dd><a href="match_patterns.html">URL patterns</a> like
+  <code>*://www.google.com/foo*bar</code>, <code>chrome-extension://*/*</code>.

[Aaron Boodman, 2011/12/06 06:43:23]

I don't think that you should call out chrome-extension:// here since it is such
an edge case.

Instead, I think we should do a quick spruce of the match pattern docs
throughout.

In match_pattern.html, it should describe the general syntax, but not a lot of
specifics. It should describe that some parts can be allowed or not allowed
depending on the API.

In each API that uses match patterns, it should describe the specifics of what
is legal. That is where you could mention chrome-extension:// for web request.

[battre, 2011/12/06 12:51:35]

Done.

+  </dd>
   <dt>Types</dt>
   <dd>Request types like <code>main_frame</code> (a document that is loaded for
   a top-level frame), <code>sub_frame</code> (a document that is loaded for an