Support chrome-extension:// scheme in URLPattern.

chrome/common/extensions/docs/webRequest.html

Index: chrome/common/extensions/docs/webRequest.html
diff --git a/chrome/common/extensions/docs/webRequest.html b/chrome/common/extensions/docs/webRequest.html
index 582660b5bab711b6150dee633b6b55560df5fced..031721234d0efa1f556bf7e72ce98d0c968fb9ce 100644
--- a/chrome/common/extensions/docs/webRequest.html
+++ b/chrome/common/extensions/docs/webRequest.html
@@ -668,7 +668,9 @@ explicitly requested.</p>
 triggered in various dimensions:
 </p><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>.

[palmer, 2011/12/05 21:33:59]

Is "chrome-extension://*/*" actually legal, though? Do you have to register to
handle a specific extension ID, or can you really register to handle all
extensions?

If you always need to give an ID, and I think? you should, document it that way
(as you do in the CL comment).

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

We filter network events by URLPattern *and* make sure for chrome-extension://
URLs that only requests the the same extension are visible.
You don't need to always give an ID. All requests to non-matching extensions are
just ignored.

+  </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