Rename chrome.experimental.webRequest to chrome.webRequest and chrome.webRequestBlocking

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

 <div id="pageData-name" class="pageData">WebRequest API</div>
 
 <!-- BEGIN AUTHORED CONTENT -->
 <p id="classSummary">
-Use the <code>chrome.experimental.webRequest</code> module to intercept, block,
+Use the <code>chrome.webRequest</code> module to intercept, block,
 or modify requests in-flight. This module is still experimental. For
 information on how to use experimental APIs, see the
 <a href="experimental.html">chrome.experimental.* APIs</a> page.
 </p>
 
 <h2 id="manifest">Manifest</h2>
-<p>You must declare the "experimental" permission in the <a
+<p>You must declare the "webRequest" permission in the <a
   href="manifest.html">extension manifest</a> to use the webRequest settings
 API, along with <a href="manifest.html#permissions">host permissions</a>
-for any hosts whose network requests you want to access.
+for any hosts whose network requests you want to access. If you want to
+use the webRequest API in a blocking fashion, you need to request
+the "webRequestBlocking" permission in addition.
 For example:</p>
 <pre>{
   "name": "My extension",
   ...
   <b>"permissions": [
-    "experimental",
+    "webRequest",
     "*://*.google.com"
   ]</b>,
   ...
 }</pre>
 
 <h2 id="life_cycle">Life-cycle of requests</h2>
 
 <p>
 The webRequest API defines the following events:
 <dl>
@@ skipping 116 matching lines @@
 
 <p>Each request is identified by a request ID. This ID is unique within a
 browser session and the context of an extension. It remains constant during the
 the life-cycle of a request and can be used to match signals for the same
 request. Note that several HTTP requests are mapped to one webRequest in case of
 HTTP redirection or HTTP authentication.</p>
 
 <h3 id="subscription">Subscription</h3>
 
 <p>For each signal XXX of the webRequest API, the API provides a function
-<code>chrome.experimental.webRequest.XXX.addListener()</code> with the following
+<code>chrome.webRequest.XXX.addListener()</code> with the following
 signature.</p>
 
 <pre>
 var callback = function(details) {...};
 var opt_filter = {...};
 var opt_extraInfoSpec = [...];
 
-chrome.experimental.webRequest.XXX.addListener(
+chrome.webRequest.XXX.addListener(
   callback, opt_filter, opt_extraInfoSpec);
 </pre>
 
 <p>Each <code>addListener()</code> call takes a mandatory callback function as
 the first parameter. This callback function is passed a dictionary containing
 information about the current URL request. The information in this dictionary
 depends on the specific event type as well as the content of
 <code>opt_extraInfoSpec</code>.</p>
 
 <p>If the optional <code>opt_extraInfoSpec</code> array contains the string
@@ skipping 40 matching lines @@
 redirect has been ignored.</p>
 
 <h2>A note about caching</h2>
 <p>
 Chrome employs two caches, an on-disk cache and a very fast in-memory cache.
 The life-time of an in-memory cache is attached to the life-time of a render
 process which roughly corresponds to a tab. Requests that are answered from the
 in-memory cache are invisible to the webRequest API. If a request handler
 changes its behavior (for example the behavior according to which requests are
 blocked), a simple page refresh might not respect this changed behavior.
-<code>chrome.experimental.webRequest.handlerBehaviorChanged()</code> needs to be
+<code>chrome.webRequest.handlerBehaviorChanged()</code> needs to be
 called to flush the in-memory cache. This is a very expensive operation and
 should not be done often.
 </p>
 
 <h2>A note about timestamps</h2>
 <p>
 It's important to note that some technical oddities in the OS's handling
 of distinct Chrome processes can cause the clock to be skewed between the
 browser itself and extension processes. That means that WebRequest's events'
 <code>timeStamp</code> property is only guaranteed to be <i>internally</i>
 consistent. Comparing one event to another event will give you the correct
 offset between them, but comparing them to the current time inside the
 extension (via <code>(new Date()).getTime()</code>, for instance) might give
 unexpected results.
 </p>
 
 <h2 id="examples">Examples</h2>
 
 <p>The following example illustrates how to block all requests to
 <code>www.evil.com</code>:</p>
 <pre>
-chrome.experimental.webRequest.onBeforeRequest.addListener(
+chrome.webRequest.onBeforeRequest.addListener(
   function(details) {
     return {cancel: details.url.indexOf("://www.evil.com/") != -1};
   },
   {},
   ["blocking"]);
 </pre>
 
+<p>As this function uses a blocking signal handler, it requires the "webRequest"
+as well as the "webRequestBlocking" permission in the manifest file.</p>
+
 <p>The following example achives the same goal in a more efficient way because
 requests that are not targeted to <code>www.evil.com</code> do not need to be
 passed to the extension:</p>
 <pre>
-chrome.experimental.webRequest.onBeforeRequest.addListener(
+chrome.webRequest.onBeforeRequest.addListener(
   function(details) { return {cancel: true}; },
   {urls: ["*://www.evil.com/*"]},
   ["blocking"]);
 </pre>
 
 <p>The following example illustrates how the User-Agent header can be deleted
 from all requests:</p>
 <pre>
-chrome.experimental.webRequest.onBeforeSendHeaders.addListener(
+chrome.webRequest.onBeforeSendHeaders.addListener(
   function(details) {
     delete details.requestHeaders['User-Agent'];
     return {requestHeaders: details.requestHeaders};
   },
   {},
   ["blocking"]);
 </pre>
 
 <!--
 TODO(mkwst): update this section. We do not pass windowIds any more.
@@ skipping 12 matching lines @@
   if (!frameUrl[windowId]) {
     frameUrl[windowId] = {};
   }
   frameUrl[windowId][tabId + "-" + frameId] = frameUrl;
 }
 
 function getFrameUrl(windowId, tabId, frameId, frameUrl) {
   return (frameUrl[windowId] || {})[tabId + "-" + frameId];
 }
 
-chrome.experimental.webRequest.onBeforeRequest.addListener(
+chrome.webRequest.onBeforeRequest.addListener(
   function(d) {
     if (d.type == 'main_frame' || d.type == 'sub_frame') {
       recordFrameUrl(d.windowId, d.tabId, d.frameId, d.frameUrl);
     }
     var frameUrl = getFrameUrl(d.windowId, d.tabId, d.frameId);
     // Use the frameUrl e.g. to selectively cancel requests.
     // Attention: The frameUrl can be undefined in some cases. Requests may not
     // originate from a frame (e.g. requests from extensions or shared workers).
   });
 
 chrome.windows.onRemoved.addListener(
   function(windowId) {delete frameUrl[windowId];}
   );
 </pre>
 -->
 <!-- END AUTHORED CONTENT -->