Fix outdated documentation on blocking start and handling of synchronous requests

BUG=none

Review URL: https://chromiumcodereview.appspot.com/10836127

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

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

@@ -302,14 +302,6 @@ For example:</p>
   ]</b>,
   ...
 }</pre>
-<p class="note">
-<b>Node:</b> If you request the "webRequestBlocking" permission, web requests
-are delayed until the background page of your extension has been loaded. This
-allows you to register event listeners before any web requests are processed.
-In order to avoid deadlocks, you must not start synchronous XmlHttpRequests or
-include scripts from the internet via <code>&lt;script src="..."&gt;</code> tags
-in your background page.
-</p>
 <h2 id="life_cycle">Life cycle of requests</h2>
 <p>
 The web request API defines a set of events that follow the life cycle of a web
@@ -411,7 +403,9 @@ are hidden, e.g.,
 <code>other_extension_id</code> is not the ID of the extension to handle
 the request,
 <code>https://www.google.com/chrome</code>,
-and others (this list is not complete).
+and others (this list is not complete). Also synchronous XMLHttpRequests from
+your extension are hidden from blocking event handlers in order to prevent
+deadlocks.
 </p>
 <h2 id="concepts">Concepts</h2>
 <p>As the following sections explain, events in the web request API use request

chrome/common/extensions/docs/samples.json

@@ -1413,7 +1413,7 @@
         "chrome.tabs.update",
         "chrome.webNavigation.onDOMContentLoaded"
       ],
-      "crx_path": "examples/extensions/gmail.crx",
+      "crx_path": null,
       "description": "Displays the number of unread messages in your Google Mail inbox. You can also click the button to open your inbox.",
       "features": [
         "alarms",

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

@@ -24,15 +24,6 @@ For example:</p>
   ...
 }</pre>
 
-<p class="note">
-<b>Node:</b> If you request the "webRequestBlocking" permission, web requests
-are delayed until the background page of your extension has been loaded. This
-allows you to register event listeners before any web requests are processed.
-In order to avoid deadlocks, you must not start synchronous XmlHttpRequests or
-include scripts from the internet via <code>&lt;script src="..."&gt;</code> tags
-in your background page.
-</p>
-
 <h2 id="life_cycle">Life cycle of requests</h2>
 
 <p>
@@ -144,7 +135,9 @@ are hidden, e.g.,
 <code>other_extension_id</code> is not the ID of the extension to handle
 the request,
 <code>https://www.google.com/chrome</code>,
-and others (this list is not complete).
+and others (this list is not complete). Also synchronous XMLHttpRequests from
+your extension are hidden from blocking event handlers in order to prevent
+deadlocks.
 </p>
 
 <h2 id="concepts">Concepts</h2>