Extension Docs: Document asyncBlocking in the Web Request API Docs.

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

Index: chrome/common/extensions/docs/templates/intros/webRequest.html
diff --git a/chrome/common/extensions/docs/templates/intros/webRequest.html b/chrome/common/extensions/docs/templates/intros/webRequest.html
index 1f578c501ba50c7049b8b3d87722cd5fef82cb6e..c6d1fb8ba5e27c498e484a4bfd496548a48cac26 100644
--- a/chrome/common/extensions/docs/templates/intros/webRequest.html
+++ b/chrome/common/extensions/docs/templates/intros/webRequest.html
@@ -210,6 +210,13 @@ request or modifying headers (<code>onBeforeSendHeaders</code>,
 <code>onHeadersReceived</code>), or providing authentication credentials
 (<code>onAuthRequired</code>).</p>
 
+<p>If the optional <code>opt_extraInfoSpec</code> array contains the string
+<code>'asyncBlocking'</code> instead (only allowed for
+<code>onAuthRequired</code>), the extension can generate the

[lazyboy, 2017/02/24 00:17:22]

<code>onAuthRequired</code> event), ...
nit: change to "the extension can generate $(ref:..BlockingResponse)
asynchronously"
(i.e. no "object").
Remove everything else after ", unlike the ..." because we've already covered
that above, right?

[karandeepb, 2017/02/24 01:04:39]

Done.

+$(ref:webRequest.BlockingResponse) object asynchronously, unlike the
+<code>'blocking'</code> mode where the callback has to synchronously return the
+$(ref:webRequest.BlockingResponse).</p>
+
 <p>The $(ref:webRequest.RequestFilter)
 <code>filter</code> allows limiting the requests for which events are
 triggered in various dimensions: