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 d5234af635f65008a52cb363d109d7d67b992699..9bbcb7fe00d7c828639e62dd2bdd18e720de1dc8 100644 |
--- a/chrome/common/extensions/docs/templates/intros/webRequest.html |
+++ b/chrome/common/extensions/docs/templates/intros/webRequest.html |
@@ -219,7 +219,7 @@ if explicitly requested.</p> |
<p>Several implementation details can be important to understand when developing |
an extension that uses the web request API:</p> |
-<h3>Conflict resolution</h3> |
+<h3 id="conflict_resolution">Conflict resolution</h3> |
<p>In the current implementation of the web request API, a request is considered |
as cancelled if at least one extension instructs to cancel the request. If |
an extension cancels a request, all extensions are notified by an |
@@ -229,7 +229,7 @@ modify the request, the most recently installed extension wins and all others |
are ignored. An extension is not notified if its instruction to modify or |
redirect has been ignored.</p> |
-<h3>Caching</h3> |
+<h3 id="caching">Caching</h3> |
<p> |
Chrome employs two caches — an on-disk cache and a very fast in-memory |
cache. The lifetime of an in-memory cache is attached to the lifetime of a |
@@ -243,7 +243,7 @@ it often; flushing the cache is a very expensive operation. You don't need to |
call <code>handlerBehaviorChanged()</code> after registering or unregistering an |
event listener.</p> |
-<h3>Timestamps</h3> |
+<h3 id="timestamps">Timestamps</h3> |
<p> |
The <code>timestamp</code> property of web request events is only guaranteed to |
be <i>internally</i> consistent. Comparing one event to another event will give |
@@ -296,4 +296,4 @@ chrome.webRequest.onBeforeSendHeaders.addListener( |
</pre> |
<p> For more example code, see the <a href="samples.html#webrequest">web request |
-samples</a>.</p> |
+samples</a>.</p> |