[html5] r8452 - [giow] (0) Remove support for receiving an error message when a port's other sid [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Feb 3 12:29:59 PST 2014
Author: ianh
Date: 2014-02-03 12:29:58 -0800 (Mon, 03 Feb 2014)
New Revision: 8452
Modified:
complete.html
index
source
Log:
[giow] (0) Remove support for receiving an error message when a port's other side is destroyed by the OS, due to lack of implementation interest.
Affected topics: DOM APIs
Modified: complete.html
===================================================================
--- complete.html 2014-02-03 19:55:03 UTC (rev 8451)
+++ complete.html 2014-02-03 20:29:58 UTC (rev 8452)
@@ -81343,8 +81343,8 @@
// event handlers
attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-messageport-onmessage title=handler-MessagePort-onmessage>onmessage</a>;
- attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-messageport-onerror title=handler-MessagePort-onerror>onerror</a>;
-};
+<!--ILLFATED attribute <span>EventHandler</span> <span title="handler-MessagePort-onerror">onerror</span>;
+-->};
// <a href=#messageport>MessagePort</a> implements <a href=#transferable>Transferable</a>;</pre>
<dl class=domintro><dt><var title="">port</var> . <code title=dom-MessagePort-postMessage><a href=#dom-messageport-postmessage>postMessage</a></code>(<var title="">message</var> [, <var title="">transfer</var>] )</dt>
@@ -81470,14 +81470,16 @@
specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, associating 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>
<!--CLEANUP-->
- <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><a href=#event-error>error</a></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>. If the <var title="">new port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>
- specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, 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>
+<!--ILLFATED
+ <li><p>If <var title="">original port</var> is <span>related to an ill-fated port</span>, then
+ create a <span title="concept-task">task</span> that <span title="fire a simple event">fires a
+ simple event</span> named <code title="event-error">error</code> at the <var title="">new
+ port</var>, and add the <span title="concept-task">task</span> to the <span>port message
+ queue</span> of <var title="">new port</var>. If the <var title="">new port</var>'s <span title="concept-port-owner">owner</span>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span title="concept-task">task</span> must
+ be associated with the <span>responsible document</span> specified by <var title="">new
+ port</var>'s <span title="concept-port-owner">owner</span>.</p></li>
+-->
<li>
@@ -81697,38 +81699,52 @@
disentangle the two ports. If the method is called on a port that is not entangled, then the
method must do nothing.</p>
- <hr><p>In some circumstances, an entangled <code><a href=#messageport>MessagePort</a></code> <var title="">source port</var>
- that is not <a href=#ports-and-garbage-collection>eligible for garbage collection</a> will
+<!--ILLFATED (search for '- -')
+ <hr>
+
+ <p>In some circumstances, an entangled <code>MessagePort</code> <var title="">source port</var>
+ that is not <a href="#ports-and-garbage-collection">eligible for garbage collection</a> will
nonetheless find itself prematurely destroyed, for example if the user manually terminates the
user agent's host process. Under such circumstances, user agents should attempt to following these
steps:</p>
- <!-- don't fire this for navigation, it would break bfcache -->
- <!-- for consistency, we don't fire this for worker termination -->
- <!-- we don't fire it on .close() because that would let you probe GC behaviour also -->
+ <!- - don't fire this for navigation, it would break bfcache - ->
+ <!- - for consistency, we don't fire this for worker termination - ->
+ <!- - we don't fire it on .close() because that would let you probe GC behaviour also - ->
- <ol><li><p>Let <var title="">target port</var> be the port with which the ill-fated <var title="">source port</var> is entangled.</li>
+ <ol>
+ <li><p>Let <var title="">target port</var> be the port with which the ill-fated <var
+ title="">source port</var> is entangled.</p></li>
+
<li><p>If there is no <var title="">target port</var> (i.e. if <var title="">source port</var>
- 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>
+ 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.</p></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>
+ <li><p>Mark <var title="">target port</var> as being a <dfn>related to an ill-fated
+ port</dfn>.</p></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><a href=#event-error>error</a></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>. If the <var title="">new port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>
- specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, 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>
+CLEANUP
+ <li><p>Create a <span title="concept-task">task</span> that <span title="fire a simple
+ event">fires a simple event</span> named <code title="event-error">error</code> at <var
+ title="">target port</var>, and add the <span title="concept-task">task</span> to the
+ <span>port message queue</span> of <var title="">target port</var>. If the <var title="">new port</var>'s <span title="concept-port-owner">owner</span>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span
+ title="concept-task">task</span> must be associated with the <span>responsible document</span>
+ specified by <var title="">source port</var>'s <span
+ title="concept-port-owner">owner</span>.</p></li>
- <li><p>Disentangle the two ports.</li>
+ <li><p>Disentangle the two ports.</p></li>
- </ol><p class=note>This does not happen if the port is garbage collected or closed using the <code title=dom-messageport-close><a href=#dom-messageport-close>close()</a></code> method. It is intended only as a way for Web
+ </ol>
+
+ <p class="note">This does not happen if the port is garbage collected or closed using the <code
+ title="dom-messageport-close">close()</code> method. It is intended only as a way for Web
applications that operate across multiple browser processes (e.g. using workers or communicating
across multiple tabs) to gracefully handle a catastrophic failure in one process. A strictly
conforming user agent would never fail unexpectedly, and thus would never send this event!</p>
+-->
<hr><p>The following are the <a href=#event-handlers>event handlers</a> (and their corresponding <a href=#event-handler-event-type title="event
handler event type">event handler event types</a>) that must be supported, as <a href=#event-handler-idl-attributes>event
@@ -81737,8 +81753,8 @@
<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a>
<tbody><tr><td><dfn id=handler-messageport-onmessage title=handler-MessagePort-onmessage><code>onmessage</code></dfn> <td> <code title=event-message><a href=#event-message>message</a></code>
- <tr><td><dfn id=handler-messageport-onerror title=handler-MessagePort-onerror><code>onerror</code></dfn> <td> <code title=event-error><a href=#event-error>error</a></code>
- </table><p>The first time a <code><a href=#messageport>MessagePort</a></code> object's <code title=handler-MessagePort-onmessage><a href=#handler-messageport-onmessage>onmessage</a></code> IDL attribute is set, the port's <a href=#port-message-queue>port
+<!--ILLFATED <tr><td><dfn title="handler-MessagePort-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
+--> </table><p>The first time a <code><a href=#messageport>MessagePort</a></code> object's <code title=handler-MessagePort-onmessage><a href=#handler-messageport-onmessage>onmessage</a></code> IDL attribute is set, the port's <a href=#port-message-queue>port
message queue</a> must be enabled, as if the <code title=dom-MessagePort-start><a href=#dom-messageport-start>start()</a></code>
method had been called.</p>
Modified: index
===================================================================
--- index 2014-02-03 19:55:03 UTC (rev 8451)
+++ index 2014-02-03 20:29:58 UTC (rev 8452)
@@ -81343,8 +81343,8 @@
// event handlers
attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-messageport-onmessage title=handler-MessagePort-onmessage>onmessage</a>;
- attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-messageport-onerror title=handler-MessagePort-onerror>onerror</a>;
-};
+<!--ILLFATED attribute <span>EventHandler</span> <span title="handler-MessagePort-onerror">onerror</span>;
+-->};
// <a href=#messageport>MessagePort</a> implements <a href=#transferable>Transferable</a>;</pre>
<dl class=domintro><dt><var title="">port</var> . <code title=dom-MessagePort-postMessage><a href=#dom-messageport-postmessage>postMessage</a></code>(<var title="">message</var> [, <var title="">transfer</var>] )</dt>
@@ -81470,14 +81470,16 @@
specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, associating 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>
<!--CLEANUP-->
- <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><a href=#event-error>error</a></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>. If the <var title="">new port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>
- specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, 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>
+<!--ILLFATED
+ <li><p>If <var title="">original port</var> is <span>related to an ill-fated port</span>, then
+ create a <span title="concept-task">task</span> that <span title="fire a simple event">fires a
+ simple event</span> named <code title="event-error">error</code> at the <var title="">new
+ port</var>, and add the <span title="concept-task">task</span> to the <span>port message
+ queue</span> of <var title="">new port</var>. If the <var title="">new port</var>'s <span title="concept-port-owner">owner</span>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span title="concept-task">task</span> must
+ be associated with the <span>responsible document</span> specified by <var title="">new
+ port</var>'s <span title="concept-port-owner">owner</span>.</p></li>
+-->
<li>
@@ -81697,38 +81699,52 @@
disentangle the two ports. If the method is called on a port that is not entangled, then the
method must do nothing.</p>
- <hr><p>In some circumstances, an entangled <code><a href=#messageport>MessagePort</a></code> <var title="">source port</var>
- that is not <a href=#ports-and-garbage-collection>eligible for garbage collection</a> will
+<!--ILLFATED (search for '- -')
+ <hr>
+
+ <p>In some circumstances, an entangled <code>MessagePort</code> <var title="">source port</var>
+ that is not <a href="#ports-and-garbage-collection">eligible for garbage collection</a> will
nonetheless find itself prematurely destroyed, for example if the user manually terminates the
user agent's host process. Under such circumstances, user agents should attempt to following these
steps:</p>
- <!-- don't fire this for navigation, it would break bfcache -->
- <!-- for consistency, we don't fire this for worker termination -->
- <!-- we don't fire it on .close() because that would let you probe GC behaviour also -->
+ <!- - don't fire this for navigation, it would break bfcache - ->
+ <!- - for consistency, we don't fire this for worker termination - ->
+ <!- - we don't fire it on .close() because that would let you probe GC behaviour also - ->
- <ol><li><p>Let <var title="">target port</var> be the port with which the ill-fated <var title="">source port</var> is entangled.</li>
+ <ol>
+ <li><p>Let <var title="">target port</var> be the port with which the ill-fated <var
+ title="">source port</var> is entangled.</p></li>
+
<li><p>If there is no <var title="">target port</var> (i.e. if <var title="">source port</var>
- 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>
+ 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.</p></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>
+ <li><p>Mark <var title="">target port</var> as being a <dfn>related to an ill-fated
+ port</dfn>.</p></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><a href=#event-error>error</a></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>. If the <var title="">new port</var>'s <a href=#concept-port-owner title=concept-port-owner>owner</a>
- specifies a <a href=#responsible-event-loop>responsible event loop</a> that is a <a href=#browsing-context>browsing context</a> <a href=#event-loop>event loop</a>, 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>
+CLEANUP
+ <li><p>Create a <span title="concept-task">task</span> that <span title="fire a simple
+ event">fires a simple event</span> named <code title="event-error">error</code> at <var
+ title="">target port</var>, and add the <span title="concept-task">task</span> to the
+ <span>port message queue</span> of <var title="">target port</var>. If the <var title="">new port</var>'s <span title="concept-port-owner">owner</span>
+ specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, the <span
+ title="concept-task">task</span> must be associated with the <span>responsible document</span>
+ specified by <var title="">source port</var>'s <span
+ title="concept-port-owner">owner</span>.</p></li>
- <li><p>Disentangle the two ports.</li>
+ <li><p>Disentangle the two ports.</p></li>
- </ol><p class=note>This does not happen if the port is garbage collected or closed using the <code title=dom-messageport-close><a href=#dom-messageport-close>close()</a></code> method. It is intended only as a way for Web
+ </ol>
+
+ <p class="note">This does not happen if the port is garbage collected or closed using the <code
+ title="dom-messageport-close">close()</code> method. It is intended only as a way for Web
applications that operate across multiple browser processes (e.g. using workers or communicating
across multiple tabs) to gracefully handle a catastrophic failure in one process. A strictly
conforming user agent would never fail unexpectedly, and thus would never send this event!</p>
+-->
<hr><p>The following are the <a href=#event-handlers>event handlers</a> (and their corresponding <a href=#event-handler-event-type title="event
handler event type">event handler event types</a>) that must be supported, as <a href=#event-handler-idl-attributes>event
@@ -81737,8 +81753,8 @@
<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a>
<tbody><tr><td><dfn id=handler-messageport-onmessage title=handler-MessagePort-onmessage><code>onmessage</code></dfn> <td> <code title=event-message><a href=#event-message>message</a></code>
- <tr><td><dfn id=handler-messageport-onerror title=handler-MessagePort-onerror><code>onerror</code></dfn> <td> <code title=event-error><a href=#event-error>error</a></code>
- </table><p>The first time a <code><a href=#messageport>MessagePort</a></code> object's <code title=handler-MessagePort-onmessage><a href=#handler-messageport-onmessage>onmessage</a></code> IDL attribute is set, the port's <a href=#port-message-queue>port
+<!--ILLFATED <tr><td><dfn title="handler-MessagePort-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
+--> </table><p>The first time a <code><a href=#messageport>MessagePort</a></code> object's <code title=handler-MessagePort-onmessage><a href=#handler-messageport-onmessage>onmessage</a></code> IDL attribute is set, the port's <a href=#port-message-queue>port
message queue</a> must be enabled, as if the <code title=dom-MessagePort-start><a href=#dom-messageport-start>start()</a></code>
method had been called.</p>
Modified: source
===================================================================
--- source 2014-02-03 19:55:03 UTC (rev 8451)
+++ source 2014-02-03 20:29:58 UTC (rev 8452)
@@ -91262,8 +91262,8 @@
// event handlers
attribute <span>EventHandler</span> <span data-x="handler-MessagePort-onmessage">onmessage</span>;
- attribute <span>EventHandler</span> <span data-x="handler-MessagePort-onerror">onerror</span>;
-};
+<!--ILLFATED attribute <span>EventHandler</span> <span data-x="handler-MessagePort-onerror">onerror</span>;
+-->};
// <span>MessagePort</span> implements <span>Transferable</span>;</pre>
<dl class="domintro">
@@ -91408,6 +91408,7 @@
data-x="">new port</var>'s <span data-x="concept-port-owner">owner</span>.</p></li>
<!--CLEANUP-->
+<!--ILLFATED
<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
@@ -91416,6 +91417,7 @@
specifies a <span>responsible event loop</span> that is a <span>browsing context</span> <span>event loop</span>, 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>
@@ -91671,6 +91673,7 @@
disentangle the two ports. If the method is called on a port that is not entangled, then the
method must do nothing.</p>
+<!--ILLFATED (search for '- -')
<hr>
<p>In some circumstances, an entangled <code>MessagePort</code> <var data-x="">source port</var>
@@ -91679,9 +91682,9 @@
user agent's host process. Under such circumstances, user agents should attempt to following these
steps:</p>
- <!-- don't fire this for navigation, it would break bfcache -->
- <!-- for consistency, we don't fire this for worker termination -->
- <!-- we don't fire it on .close() because that would let you probe GC behaviour also -->
+ <!- - don't fire this for navigation, it would break bfcache - ->
+ <!- - for consistency, we don't fire this for worker termination - ->
+ <!- - we don't fire it on .close() because that would let you probe GC behaviour also - ->
<ol>
@@ -91696,7 +91699,7 @@
<li><p>Mark <var data-x="">target port</var> as being a <dfn>related to an ill-fated
port</dfn>.</p></li>
-<!--CLEANUP-->
+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 the <span data-x="concept-task">task</span> to the
@@ -91715,6 +91718,7 @@
applications that operate across multiple browser processes (e.g. using workers or communicating
across multiple tabs) to gracefully handle a catastrophic failure in one process. A strictly
conforming user agent would never fail unexpectedly, and thus would never send this event!</p>
+-->
<hr>
@@ -91728,8 +91732,8 @@
<tr><th><span data-x="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn data-x="handler-MessagePort-onmessage"><code>onmessage</code></dfn> <td> <code data-x="event-message">message</code>
- <tr><td><dfn data-x="handler-MessagePort-onerror"><code>onerror</code></dfn> <td> <code data-x="event-error">error</code>
- </table>
+<!--ILLFATED <tr><td><dfn data-x="handler-MessagePort-onerror"><code>onerror</code></dfn> <td> <code data-x="event-error">error</code>
+--> </table>
<p>The first time a <code>MessagePort</code> object's <code
data-x="handler-MessagePort-onmessage">onmessage</code> IDL attribute is set, the port's <span>port
More information about the Commit-Watchers
mailing list