Index: chrome/common/extensions/docs/templates/intros/webNavigation.html |
diff --git a/chrome/common/extensions/docs/templates/intros/webNavigation.html b/chrome/common/extensions/docs/templates/intros/webNavigation.html |
index 36e3136b40279e1f6223f48593ec11dabf7ac166..e7c25c671d6adcfe5a268bdaabae15cba157b180 100644 |
--- a/chrome/common/extensions/docs/templates/intros/webNavigation.html |
+++ b/chrome/common/extensions/docs/templates/intros/webNavigation.html |
@@ -103,7 +103,7 @@ extension (via <code>(new Date()).getTime()</code>, for instance) might give |
unexpected results. |
</p> |
-<h2 id="frame_ids">A note about frame and process IDs</h2> |
+<h2 id="frame_ids">A note about frame IDs</h2> |
<p> |
Frames within a tab can be identified by a frame ID. The frame ID of the main |
frame is always 0, the ID of child frames is a positive number. Once a document |
Devlin
2015/10/30 01:49:39
If frame ID uniquely identifies the frame, it impl
battre
2015/11/02 13:54:57
So this is a non-backwards compatible change, righ
Devlin
2015/11/02 17:07:16
I don't think this should really be a problem. No
battre
2015/11/02 17:18:22
My concern was the "The frame ID of the main frame
Devlin
2015/11/02 17:28:47
Oh, whoops (yay for Monday mornings). Good point.
robwu
2015/11/02 19:08:34
Done. I waited with updating this section until th
battre
2015/11/03 09:07:19
My backwards compatibility concern is that in the
robwu
2015/11/03 10:03:02
frameId 0 is still the main frame. The semantics h
|
@@ -111,15 +111,6 @@ is constructed in a frame, its frame ID remains constant during the lifetime of |
the document. |
</p> |
<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 |