summaryrefslogtreecommitdiffstats
path: root/chrome/common/extensions/docs/static/experimental.webNavigation.html
blob: 3f214adcfcc0f998c8d802eb074255b29fe91155 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<div id="pageData-name" class="pageData">WebNavigation API</div>

<!-- BEGIN AUTHORED CONTENT -->
<p id="classSummary">
Use the <code>chrome.experimental.webNavigation</code> module to recieve
notifications about the status of navigations requests in-flight. This
module is still very much experimental. For information on how to use
experimental APIs, see the <a href="experimental.html">chrome.experimental.*
APIs</a> page.
</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 WebNavigation'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>
<!-- END AUTHORED CONTENT -->