[html5] r8342 - [giow] (0) Make sure subsequent owners of an ill-fated port's friend can know ab [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Dec 11 11:51:52 PST 2013
Author: ianh
Date: 2013-12-11 11:51:50 -0800 (Wed, 11 Dec 2013)
New Revision: 8342
Modified:
complete.html
index
source
Log:
[giow] (0) Make sure subsequent owners of an ill-fated port's friend can know about that fate
Affected topics: DOM APIs
Modified: complete.html
===================================================================
--- complete.html 2013-12-11 17:41:24 UTC (rev 8341)
+++ complete.html 2013-12-11 19:51:50 UTC (rev 8342)
@@ -80570,11 +80570,21 @@
<li><p>Set <var title="">new port</var>'s <a href=#has-been-shipped>has been shipped</a> flag to true.</li>
- <li><p>Move all the events in the <a href=#port-message-queue>port message queue</a> of <var title="">original
+<!--CLEANUP-->
+ <li><p>Move all the <a href=#concept-task title=concept-task>tasks</a> that are to fire <code title=event-message><a href=#event-message>message</a></code> events in the <a href=#port-message-queue>port message queue</a> of <var title="">original
port</var> to the <a href=#port-message-queue>port message queue</a> of <var title="">new port</var>, if any,
leaving the <var title="">new port</var>'s <a href=#port-message-queue>port message queue</a> in its initial
- disabled state.</li>
+ disabled state, and reassociating the moved <a href=#concept-task title=concept-task>tasks</a> with the <a href=#responsible-document>responsible document</a> specified by <var title="">new
+ port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
+ <li><p>If <var title="">original port</var> is <a href=#related-to-an-ill-fated-port>related to an ill-fated port</a>, then
+ create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a
+ simple event</a> named <code title=event-error>error</code> at the <var title="">new
+ port</var>, and add the <a href=#concept-task title=concept-task>task</a> to the <a href=#port-message-queue>port message
+ queue</a> of <var title="">new port</var>. The <a href=#concept-task title=concept-task>task</a> must
+ be associated with the <a href=#responsible-document>responsible document</a> specified by <var title="">new
+ port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
+
<li>
<p>If the <var title="">original port</var> is entangled with another port, then run these
@@ -80818,8 +80828,11 @@
is not entangled), or if <var title="">target port</var> is suffering the same fate as <var title="">source port</var> (e.g. if both ports are in the same host process), then abort these
steps.</li>
+ <li><p>Mark <var title="">target port</var> as being a <dfn id=related-to-an-ill-fated-port>related to an ill-fated
+ port</dfn>.</li>
+
<!--CLEANUP-->
- <li><p>Create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a simple event</a> named <code title=event-error>error</code> at <var title="">target port</var>, and add it to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>. The <a href=#concept-task title=concept-task>task</a> must be associated with the <a href=#responsible-document>responsible document</a>
+ <li><p>Create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a simple event</a> named <code title=event-error>error</code> at <var title="">target port</var>, and add the <a href=#concept-task title=concept-task>task</a> to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>. The <a href=#concept-task title=concept-task>task</a> must be associated with the <a href=#responsible-document>responsible document</a>
specified by <var title="">source port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
<li><p>Disentangle the two ports.</li>
Modified: index
===================================================================
--- index 2013-12-11 17:41:24 UTC (rev 8341)
+++ index 2013-12-11 19:51:50 UTC (rev 8342)
@@ -80570,11 +80570,21 @@
<li><p>Set <var title="">new port</var>'s <a href=#has-been-shipped>has been shipped</a> flag to true.</li>
- <li><p>Move all the events in the <a href=#port-message-queue>port message queue</a> of <var title="">original
+<!--CLEANUP-->
+ <li><p>Move all the <a href=#concept-task title=concept-task>tasks</a> that are to fire <code title=event-message><a href=#event-message>message</a></code> events in the <a href=#port-message-queue>port message queue</a> of <var title="">original
port</var> to the <a href=#port-message-queue>port message queue</a> of <var title="">new port</var>, if any,
leaving the <var title="">new port</var>'s <a href=#port-message-queue>port message queue</a> in its initial
- disabled state.</li>
+ disabled state, and reassociating the moved <a href=#concept-task title=concept-task>tasks</a> with the <a href=#responsible-document>responsible document</a> specified by <var title="">new
+ port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
+ <li><p>If <var title="">original port</var> is <a href=#related-to-an-ill-fated-port>related to an ill-fated port</a>, then
+ create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a
+ simple event</a> named <code title=event-error>error</code> at the <var title="">new
+ port</var>, and add the <a href=#concept-task title=concept-task>task</a> to the <a href=#port-message-queue>port message
+ queue</a> of <var title="">new port</var>. The <a href=#concept-task title=concept-task>task</a> must
+ be associated with the <a href=#responsible-document>responsible document</a> specified by <var title="">new
+ port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
+
<li>
<p>If the <var title="">original port</var> is entangled with another port, then run these
@@ -80818,8 +80828,11 @@
is not entangled), or if <var title="">target port</var> is suffering the same fate as <var title="">source port</var> (e.g. if both ports are in the same host process), then abort these
steps.</li>
+ <li><p>Mark <var title="">target port</var> as being a <dfn id=related-to-an-ill-fated-port>related to an ill-fated
+ port</dfn>.</li>
+
<!--CLEANUP-->
- <li><p>Create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a simple event</a> named <code title=event-error>error</code> at <var title="">target port</var>, and add it to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>. The <a href=#concept-task title=concept-task>task</a> must be associated with the <a href=#responsible-document>responsible document</a>
+ <li><p>Create a <a href=#concept-task title=concept-task>task</a> that <a href=#fire-a-simple-event title="fire a simple event">fires a simple event</a> named <code title=event-error>error</code> at <var title="">target port</var>, and add the <a href=#concept-task title=concept-task>task</a> to the <a href=#port-message-queue>port message queue</a> of <var title="">target port</var>. The <a href=#concept-task title=concept-task>task</a> must be associated with the <a href=#responsible-document>responsible document</a>
specified by <var title="">source port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>.</li>
<li><p>Disentangle the two ports.</li>
Modified: source
===================================================================
--- source 2013-12-11 17:41:24 UTC (rev 8341)
+++ source 2013-12-11 19:51:50 UTC (rev 8342)
@@ -90286,11 +90286,21 @@
<li><p>Set <var data-x="">new port</var>'s <span>has been shipped</span> flag to true.</p></li>
- <li><p>Move all the events in the <span>port message queue</span> of <var data-x="">original
+<!--CLEANUP-->
+ <li><p>Move all the <span data-x="concept-task">tasks</span> that are to fire <code data-x="event-message">message</code> events in the <span>port message queue</span> of <var data-x="">original
port</var> to the <span>port message queue</span> of <var data-x="">new port</var>, if any,
leaving the <var data-x="">new port</var>'s <span>port message queue</span> in its initial
- disabled state.</p></li>
+ disabled state, and reassociating the moved <span data-x="concept-task">tasks</span> with the <span>responsible document</span> specified by <var data-x="">new
+ port</var>'s <span data-x="concept-port-owner">owner</span>.</p></li>
+ <li><p>If <var data-x="">original port</var> is <span>related to an ill-fated port</span>, then
+ create a <span data-x="concept-task">task</span> that <span data-x="fire a simple event">fires a
+ simple event</span> named <code data-x="event-error">error</code> at the <var data-x="">new
+ port</var>, and add the <span data-x="concept-task">task</span> to the <span>port message
+ queue</span> of <var data-x="">new port</var>. The <span data-x="concept-task">task</span> must
+ be associated with the <span>responsible document</span> specified by <var data-x="">new
+ port</var>'s <span data-x="concept-port-owner">owner</span>.</p></li>
+
<li>
<p>If the <var data-x="">original port</var> is entangled with another port, then run these
@@ -90577,9 +90587,12 @@
data-x="">source port</var> (e.g. if both ports are in the same host process), then abort these
steps.</p></li>
+ <li><p>Mark <var data-x="">target port</var> as being a <dfn>related to an ill-fated
+ port</dfn>.</p></li>
+
<!--CLEANUP-->
<li><p>Create a <span data-x="concept-task">task</span> that <span data-x="fire a simple event">fires a simple event</span> named <code
- data-x="event-error">error</code> at <var data-x="">target port</var>, and add it to the <span>port message queue</span> of <var data-x="">target port</var>. The <span
+ data-x="event-error">error</code> at <var data-x="">target port</var>, and add the <span data-x="concept-task">task</span> to the <span>port message queue</span> of <var data-x="">target port</var>. The <span
data-x="concept-task">task</span> must be associated with the <span>responsible document</span>
specified by <var data-x="">source port</var>'s <span data-x="concept-port-owner">owner</span>.</p></li>
More information about the Commit-Watchers
mailing list