Index: chrome/common/extensions/docs/templates/intros/webNavigation.html |
=================================================================== |
--- chrome/common/extensions/docs/templates/intros/webNavigation.html (revision 159603) |
+++ chrome/common/extensions/docs/templates/intros/webNavigation.html (working copy) |
@@ -3,7 +3,7 @@ |
notifications about the status of navigations requests in-flight. |
</p> |
-<h2>Manifest</h2> |
+<h2 id="manifest">Manifest</h2> |
<p> |
All <code>chrome.webNavigation</code> methods and events require you to declare |
the "webNavigation" permission in the <a href="manifest.html">extension |
@@ -21,7 +21,7 @@ |
}</pre> |
-<h2>Examples</h2> |
+<h2 id="examples">Examples</h2> |
<p> |
You can find simple examples of using the tabs module in the |
@@ -31,7 +31,7 @@ |
<a href="samples.html">Samples</a>. |
</p> |
-<h2>Event order</h2> |
+<h2 id="event_order">Event order</h2> |
<p> |
For a navigation that is successfully completed, events are fired in the |
following order: |
@@ -70,7 +70,7 @@ |
case, an <code>onTabReplaced</code> event is fired. |
</p> |
-<h2>Relation to webRequest events</h2> |
+<h2 id="relation_to_webRequest">Relation to webRequest events</h2> |
<p> |
There is no defined ordering between events of the <a |
href="webRequest.html">webRequest API</a> and the events of the |
@@ -84,7 +84,7 @@ |
the state of the network stack which is generally opaque to the user. |
</p> |
-<h2>A note about tab IDs</h2> |
+<h2 id="tab_ids">A note about tab IDs</h2> |
<p> |
Not all navigating tabs correspond to actual tabs in Chrome's UI, e.g., a tab |
that is being pre-rendered. Such tabs are not accessible via the |
@@ -94,7 +94,7 @@ |
they become accessible via these APIs. |
</p> |
-<h2>A note about timestamps</h2> |
+<h2 id="timestamps">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 |
@@ -106,7 +106,7 @@ |
unexpected results. |
</p> |
-<h2>A note about frame and process IDs</h2> |
+<h2 id="frame_ids">A note about frame and process IDs</h2> |
<p> |
Due to the multi-process nature of Chrome, a tab might use different processes |
to render the source and destination of a web page. Therefore, if a navigation |
@@ -124,7 +124,7 @@ |
<code>onCommitted</code> event. |
</p> |
-<h2>Transition types and qualifiers</h2> |
+<h2 id="transition_types">Transition types and qualifiers</h2> |
<p> |
The webNavigation API's <code>onCommitted</code> event has a |
<code>transitionType</code> and a <code>transitionQualifiers</code> property. |
@@ -166,4 +166,4 @@ |
The user initiated the navigation from the address bar (aka Omnibox). |
</td> |
</tr> |
-</table> |
+</table> |