Almost all actions in Declarative Web Request require all_urls host permissions

chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html

Index: chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
diff --git a/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html b/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
index c9a295ff29e86ae4d46198c493ac7ac275a507cc..c0474088e912592d3290f2bae203a3998a4b32d3 100644
--- a/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
+++ b/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
@@ -14,8 +14,7 @@ efficiency.
 <p>
 You must declare the "declarativeWebRequest" permission in the
 <a href="manifest.html">extension manifest</a> to use this API,
-along with <a href="declare_permissions.html">host permissions</a> for any
-hosts whose network requests you want to access.
+along with <a href="declare_permissions.html">host permissions</a>.
 </p>
 
 <pre>{
@@ -29,18 +28,29 @@ hosts whose network requests you want to access.
 }</pre>
 
 <p>
-Note that certain types of non-sensitive requests do not require host
+Note that certain types of non-sensitive actions do not require host
 permissions:
+</p>
 <ul>
   <li><code>CancelRequest</code>
   <li><code>IgnoreRules</code>
   <li><code>RedirectToEmptyDocument</code>
   <li><code>RedirectToTransparentImage</code>
-  <li><code>RedirectByRegEx</code> when the redirect destination has
-    the same domain as the original request
-  <li><code>RedirectRequest</code> when the redirect destination has
-    the same domain as the original request
 </ul>
+<p>
+The <code>SendMessageToExtension</code> action requires host permissions
+for any hosts whose network requests you want to trigger a message.
+</p>
+<p>
+All other actions require host permissions to all URLs.
+</p>
+<p>
+As an example, if <code>"*://*.google.com"</code> is the only host permission an
+extension has, than such an extension may set up a rule to cancel a request to
+"http://www.google.com", it also may set up a rule to send a message to this

[Matt Perry, 2013/04/19 21:55:28]

nit: restruct a bit to, 'such an extension may set up a rule to
* cancel a request to "http://www.google.com" or "http://anything.else.com"'
* send a message when navigating to "http://www.google.com" but not to
"http://something.else.com"
The extension cannot set up a rule to redirect...'

[vabr (Chromium), 2013/04/25 19:08:03]

Done.

+extension if there is such request, but it cannot set up a rule to redirect
+"http://www.google.com" to "http://mail.google.com".
+</p>
 
 <h2 id="rules">Rules</h2>