chrome/common/extensions/docs/static/webNavigation.html - Issue 10807009: Include the processId in webNavigation events

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome/common/extensions/docs/static/webNavigation.html

Issue 10807009: Include the processId in webNavigation events (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 8 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/common/extensions/docs/extensions/webNavigation.html ('k') | chrome/test/data/extensions/api_test/webnavigation/framework.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: chrome/common/extensions/docs/static/webNavigation.html

diff --git a/chrome/common/extensions/docs/static/webNavigation.html b/chrome/common/extensions/docs/static/webNavigation.html

index 3dbbd8060e862aa644256f334629f3f2cf1ea6dd..0774725f0104b15a845f4e55fd6d980533b4d619 100644

--- a/chrome/common/extensions/docs/static/webNavigation.html

+++ b/chrome/common/extensions/docs/static/webNavigation.html

@@ -60,6 +60,11 @@ time after <code>onDOMContentLoaded</code>, even after

<code>onCompleted</code>.

</p>

<p>

+If the history API is used to modify the state of a frame (e.g. using

+<code>history.pushState()</code>, a <code>onHistoryStateUpdated</code> event is

+fired. This event can fire any time after <code>onDOMContentLoaded</code>.

+</p>

+<p>

If a navigation was triggered via <a

href="https://support.google.com/chrome/bin/answer.py?answer=177873">Chrome

Instant</a> or <a

@@ -104,6 +109,24 @@ extension (via <code>(new Date()).getTime()</code>, for instance) might give

unexpected results.

</p>

+<h2>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

+takes place in a new process, you might receive events both from the new and

+the old page until the new navigation is committed (i.e. the

+<code>onCommitted</code> event is send for the new main frame). Because frame

+IDs are only unique for a given process, the webNavigation events include a

+process ID, so you can still determine which frame a navigation came from.

+</p>

+<p>

+Also note that during a provisional load the process might be switched several

+times. This happens when the load is redirected to a different site. In this

+case, you will receive repeated <code>onBeforeNavigate</code> and

+<code>onErrorOccurred</code> events, until you receive the final

+<code>onCommitted</code> event.

+</p>

<h2>Transition types and qualifiers</h2>

<p>

The webNavigation API's <code>onCommitted</code> event has a