[html5] r7219 - [e] (0) Fix some cross-reference issues. Affected topics: HTML, Web Workers, Web [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jul 26 22:56:59 PDT 2012
Author: ianh
Date: 2012-07-26 22:56:57 -0700 (Thu, 26 Jul 2012)
New Revision: 7219
Modified:
complete.html
index
source
Log:
[e] (0) Fix some cross-reference issues.
Affected topics: HTML, Web Workers, WebSocket API
Modified: complete.html
===================================================================
--- complete.html 2012-07-27 05:52:36 UTC (rev 7218)
+++ complete.html 2012-07-27 05:56:57 UTC (rev 7219)
@@ -58482,7 +58482,7 @@
</ol></li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> named <code title=event-close>close</code> at <var title="">dialog</var>.</li>
+ event</a> named <dfn id=event-close title=event-close><code>close</code></dfn> at <var title="">dialog</var>.</li>
</ol><!--TOPIC:DOM APIs--><p>The <dfn id=dom-dialog-returnvalue title=dom-dialog-returnValue><code>returnValue</code></dfn> IDL
attribute, on getting, must return the last value to which it was
@@ -58495,8 +58495,8 @@
<code><a href=#document>Document</a></code>'s <a href=#pending-dialog-stack>pending dialog stack</a> is not
empty, user agents may provide a user interface that, upon
activation, <a href=#queue-a-task title="queue a task">queues a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-cancel>cancel</code> that is cancelable at the top
- <code><a href=#the-dialog-element>dialog</a></code> element on the <code><a href=#document>Document</a></code>'s
+ <a href=#fire-a-simple-event>fire a simple event</a> named <dfn id=event-cancel title=event-cancel><code>cancel</code></dfn> that is cancelable at
+ the top <code><a href=#the-dialog-element>dialog</a></code> element on the <code><a href=#document>Document</a></code>'s
<a href=#pending-dialog-stack>pending dialog stack</a>. The default action of this event
must be to <a href=#close-the-dialog>close the dialog</a> with no return value.</p>
@@ -73763,7 +73763,7 @@
<tr><td><dfn id=handler-oncanplaythrough title=handler-oncanplaythrough><code>oncanplaythrough</code></dfn> <td> <code title=event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code>
<tr><td><dfn id=handler-onchange title=handler-onchange><code>onchange</code></dfn> <td> <code title=event-change>change</code> <!-- widely used -->
<tr><td><dfn id=handler-onclick title=handler-onclick><code>onclick</code></dfn> <td> <code title=event-click><a href=#event-click>click</a></code> <!-- widely used -->
- <tr><td><dfn id=handler-onclose title=handler-onclose><code>onclose</code></dfn> <td> <code title=event-close>close</code> <!-- new for <dialog> -->
+ <tr><td><dfn id=handler-onclose title=handler-onclose><code>onclose</code></dfn> <td> <code title=event-close><a href=#event-close>close</a></code> <!-- new for <dialog> -->
<tr><td><dfn id=handler-oncontextmenu title=handler-oncontextmenu><code>oncontextmenu</code></dfn> <td> <code title=event-contextmenu>contextmenu</code> <!-- widely used -->
<tr><td><dfn id=handler-oncuechange title=handler-oncuechange><code>oncuechange</code></dfn> <td> <code title=event-cuechange>cuechange</code>
<tr><td><dfn id=handler-ondblclick title=handler-ondblclick><code>ondblclick</code></dfn> <td> <code title=event-dblclick>dblclick</code> <!-- widely used -->
@@ -80738,7 +80738,7 @@
<!-- v2-onclose
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
<code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -80753,7 +80753,7 @@
interface:</p>
<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><!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> --><tr><td><dfn id=handler-workerglobalscope-onerror title=handler-WorkerGlobalScope-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
+ <tbody><!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> --><tr><td><dfn id=handler-workerglobalscope-onerror title=handler-WorkerGlobalScope-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
<tr><td><dfn id=handler-workerglobalscope-onoffline title=handler-WorkerGlobalScope-onoffline><code>onoffline</code></dfn> <td> <code title=event-offline><a href=#event-offline>offline</a></code> <!-- new -->
<tr><td><dfn id=handler-workerglobalscope-ononline title=handler-WorkerGlobalScope-ononline><code>ononline</code></dfn> <td> <code title=event-online><a href=#event-online>online</a></code> <!-- new -->
</table><h5 id=dedicated-workers-and-the-dedicatedworkerglobalscope-interface><span class=secno>9.2.1.2 </span>Dedicated workers and the <code><a href=#dedicatedworkerglobalscope>DedicatedWorkerGlobalScope</a></code> interface</h5>
@@ -81048,7 +81048,7 @@
scope</var>'s <a href=#dom-workerglobalscope-closing title=dom-WorkerGlobalScope-closing>closing</a> flag is set
to true<!-- v2-onclose and <span title="queue a task">a task is
queued</span> to <span>fire a simple event</span> named <code
- title="event-close">close</code> at <var title="">worker global
+ title="event-worker-close">close</code> at <var title="">worker global
scope</var>-->.</p>
</li>
@@ -81157,7 +81157,7 @@
<p>For each <code>Worker</code> or <code>SharedWorker</code>
object associated with <var title="">worker global scope</var>,
<span>queue a task</span> to <span>fire a simple event</span>
- named <code title="event-close">close</code> at that object.</p>
+ named <code title="event-worker-close">close</code> at that object.</p>
</li>
-->
@@ -81169,7 +81169,7 @@
<li><p>If the worker's <code>WorkerGlobalScope</code> object's
<span title="dom-WorkerGlobalScope-closing">closing</span> flag is
false, <span>queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
worker's <code>WorkerGlobalScope</code> object.</p></li>
--><li><p>Set the worker's <code><a href=#workerglobalscope>WorkerGlobalScope</a></code> object's <a href=#dom-workerglobalscope-closing title=dom-WorkerGlobalScope-closing>closing</a> flag to
true.</li>
@@ -81178,20 +81178,20 @@
<li><p>Wait a user-agent-defined amount of time. If the "<span>run
a worker</span>" processing model defined above immediately starts
running event listeners registered for the <code
- title="event-close">close</code> event, this time should not be
+ title="event-worker-close">close</code> event, this time should not be
zero — the idea is that the <code
- title="event-close">close</code> event can be used to clean up
+ title="event-worker-close">close</code> event can be used to clean up
when shutting down unexpectedly.</p></li>
-->
<li><p>If there are any <a href=#concept-task title=concept-task>tasks</a>
queued in the <a href=#event-loop>event loop</a>'s <a href=#task-queue title="task
queue">task queues</a><!-- v2-onclose other than the <code
- title="event-close">close</code> event that this algorithm just
+ title="event-worker-close">close</code> event that this algorithm just
added-->, discard them without processing them.</li>
<!-- v2-onclose
- <li><p>If the <code title="event-close">close</code> event that
+ <li><p>If the <code title="event-worker-close">close</code> event that
this algorithm just queued hasn't yet been dispatched, then abort
the script currently running in the worker.</p></li>
-->
@@ -81200,7 +81200,7 @@
<li><p>Abort the script currently running in the worker<!--
v2-onclose (if any script is running, then it will be a handler for
- the <code title="event-close">close</code> event)-->.</li>
+ the <code title="event-worker-close">close</code> event)-->.</li>
</ol><p>User agents may invoke the "<a href=#kill-a-worker>kill a worker</a>"
processing model on a worker at any time, e.g. in response to user
@@ -81326,7 +81326,7 @@
<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-abstractworker-onerror title=handler-AbstractWorker-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
-<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
+<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> -->
</table><h5 id=dedicated-workers-and-the-worker-interface><span class=secno>9.2.7.2 </span>Dedicated workers and the <code><a href=#worker>Worker</a></code> interface</h5>
<pre class=idl>[<a href=#dom-worker title=dom-Worker>Constructor</a>(DOMString scriptURL)]
@@ -83136,7 +83136,7 @@
algorithm fails, it triggers the <i><a href=#fail-the-websocket-connection>fail the WebSocket
connection</a></i> algorithm, which then invokes the <i><a href=#close-the-websocket-connection>close the
WebSocket connection</a></i> algorithm, which then establishes that
- <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</li>
@@ -83232,7 +83232,7 @@
<p>Do nothing.</p>
<p class=note>The connection is already closing or is already
- closed. If it has not already, a <code title=event-close>close</code> event will eventually fire <a href=#closeWebSocket>as described below</a>.</p>
+ closed. If it has not already, a <code title=event-socket-close>close</code> event will eventually fire <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83250,7 +83250,7 @@
algorithm invokes the <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> algorithm, which then establishes that
<i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the
- <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83274,7 +83274,7 @@
<p class=note>The <i><a href=#start-the-websocket-closing-handshake>start the WebSocket closing handshake</a></i>
algorithm eventually invokes the <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> algorithm, which then establishes that <i><a href=#the-websocket-connection-is-closed>the
- WebSocket connection is closed</a></i>, which fires the <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ WebSocket connection is closed</a></i>, which fires the <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83290,7 +83290,7 @@
<p class=note><i><a href=#the-websocket-closing-handshake-is-started>The WebSocket closing handshake is
started</a></i>, and will eventually invoke the <i><a href=#close-the-websocket-connection>close the
WebSocket connection</a></i> algorithm, which will establish that
- <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, and thus the <code title=event-close>close</code> event will fire, <a href=#closeWebSocket>as described below</a>.</p>
+ <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, and thus the <code title=event-socket-close>close</code> event will fire, <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83469,7 +83469,7 @@
<tbody><tr><td><dfn id=handler-websocket-onopen title=handler-WebSocket-onopen><code>onopen</code></dfn> <td> <code title=event-open>open</code>
<tr><td><dfn id=handler-websocket-onmessage title=handler-WebSocket-onmessage><code>onmessage</code></dfn> <td> <code title=event-message><a href=#event-message>message</a></code>
<tr><td><dfn id=handler-websocket-onerror title=handler-WebSocket-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
- <tr><td><dfn id=handler-websocket-onclose title=handler-WebSocket-onclose><code>onclose</code></dfn> <td> <code title=event-close>close</code>
+ <tr><td><dfn id=handler-websocket-onclose title=handler-WebSocket-onclose><code>onclose</code></dfn> <td> <code title=event-socket-close>close</code>
</table><h4 id=feedback-from-the-protocol><span class=secno>10.3.3 </span>Feedback from the protocol</h4>
<p>When <i><a href=#the-websocket-connection-is-established>the WebSocket connection is established</a></i>, the user
@@ -83594,7 +83594,7 @@
at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
<li><p>Create an event that uses the <code><a href=#closeevent>CloseEvent</a></code>
- interface, with the event type <code title=event-close>close</code>, which does not bubble, is not
+ interface, with the event type <code title=event-socket-close>close</code>, which does not bubble, is not
cancelable, has no default action, whose <code title=dom-CloseEvent-wasClean><a href=#dom-closeevent-wasclean>wasClean</a></code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false
otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code>
@@ -83772,18 +83772,18 @@
(0) as of the last time the <a href=#event-loop>event loop</a> started
executing a <a href=#concept-task title=concept-task>task</a> must not be
garbage collected if there are any event listeners registered for
- <code title=event-open>open</code> events, <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code> events, or <code title=event-close>close</code> events.</p>
+ <code title=event-open>open</code> events, <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code> events, or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object whose <code title=dom-WebSocket-readyState><a href=#dom-websocket-readystate>readyState</a></code> attribute's value
was set to <code title=dom-WebSocket-OPEN><a href=#dom-websocket-open>OPEN</a></code> (1) as of
the last time the <a href=#event-loop>event loop</a> started executing a <a href=#concept-task title=concept-task>task</a> must not be garbage collected if
- there are any event listeners registered for <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code>, or <code title=event-close>close</code> events.</p>
+ there are any event listeners registered for <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code>, or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object whose <code title=dom-WebSocket-readyState><a href=#dom-websocket-readystate>readyState</a></code> attribute's value
was set to <code title=dom-WebSocket-CLOSING><a href=#dom-websocket-closing>CLOSING</a></code> (2) as
of the last time the <a href=#event-loop>event loop</a> started executing a
<a href=#concept-task title=concept-task>task</a> must not be garbage collected
- if there are any event listeners registered for <code title=event-error>error</code> or <code title=event-close>close</code> events.</p>
+ if there are any event listeners registered for <code title=event-error>error</code> or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object with <i title="the WebSocket
connection is established"><a href=#the-websocket-connection-is-established>an established connection</a></i> that has
@@ -102494,7 +102494,7 @@
<tr><th id=ix-handler-onclose> <code title="">onclose</code>
<td> <a href=#handler-onclose title=handler-onclose>HTML elements</a>
- <td> <code title=event-close>close</code> event handler
+ <td> <code title=event-close><a href=#event-close>close</a></code> event handler
<td> <a href=#event-handler-content-attributes title="event handler content attributes">Event handler content attribute</a>
<tr><th id=ix-handler-oncontextmenu> <code title="">oncontextmenu</code>
Modified: index
===================================================================
--- index 2012-07-27 05:52:36 UTC (rev 7218)
+++ index 2012-07-27 05:56:57 UTC (rev 7219)
@@ -58482,7 +58482,7 @@
</ol></li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> named <code title=event-close>close</code> at <var title="">dialog</var>.</li>
+ event</a> named <dfn id=event-close title=event-close><code>close</code></dfn> at <var title="">dialog</var>.</li>
</ol><!--TOPIC:DOM APIs--><p>The <dfn id=dom-dialog-returnvalue title=dom-dialog-returnValue><code>returnValue</code></dfn> IDL
attribute, on getting, must return the last value to which it was
@@ -58495,8 +58495,8 @@
<code><a href=#document>Document</a></code>'s <a href=#pending-dialog-stack>pending dialog stack</a> is not
empty, user agents may provide a user interface that, upon
activation, <a href=#queue-a-task title="queue a task">queues a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-cancel>cancel</code> that is cancelable at the top
- <code><a href=#the-dialog-element>dialog</a></code> element on the <code><a href=#document>Document</a></code>'s
+ <a href=#fire-a-simple-event>fire a simple event</a> named <dfn id=event-cancel title=event-cancel><code>cancel</code></dfn> that is cancelable at
+ the top <code><a href=#the-dialog-element>dialog</a></code> element on the <code><a href=#document>Document</a></code>'s
<a href=#pending-dialog-stack>pending dialog stack</a>. The default action of this event
must be to <a href=#close-the-dialog>close the dialog</a> with no return value.</p>
@@ -73763,7 +73763,7 @@
<tr><td><dfn id=handler-oncanplaythrough title=handler-oncanplaythrough><code>oncanplaythrough</code></dfn> <td> <code title=event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code>
<tr><td><dfn id=handler-onchange title=handler-onchange><code>onchange</code></dfn> <td> <code title=event-change>change</code> <!-- widely used -->
<tr><td><dfn id=handler-onclick title=handler-onclick><code>onclick</code></dfn> <td> <code title=event-click><a href=#event-click>click</a></code> <!-- widely used -->
- <tr><td><dfn id=handler-onclose title=handler-onclose><code>onclose</code></dfn> <td> <code title=event-close>close</code> <!-- new for <dialog> -->
+ <tr><td><dfn id=handler-onclose title=handler-onclose><code>onclose</code></dfn> <td> <code title=event-close><a href=#event-close>close</a></code> <!-- new for <dialog> -->
<tr><td><dfn id=handler-oncontextmenu title=handler-oncontextmenu><code>oncontextmenu</code></dfn> <td> <code title=event-contextmenu>contextmenu</code> <!-- widely used -->
<tr><td><dfn id=handler-oncuechange title=handler-oncuechange><code>oncuechange</code></dfn> <td> <code title=event-cuechange>cuechange</code>
<tr><td><dfn id=handler-ondblclick title=handler-ondblclick><code>ondblclick</code></dfn> <td> <code title=event-dblclick>dblclick</code> <!-- widely used -->
@@ -80738,7 +80738,7 @@
<!-- v2-onclose
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
<code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -80753,7 +80753,7 @@
interface:</p>
<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><!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> --><tr><td><dfn id=handler-workerglobalscope-onerror title=handler-WorkerGlobalScope-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
+ <tbody><!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> --><tr><td><dfn id=handler-workerglobalscope-onerror title=handler-WorkerGlobalScope-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
<tr><td><dfn id=handler-workerglobalscope-onoffline title=handler-WorkerGlobalScope-onoffline><code>onoffline</code></dfn> <td> <code title=event-offline><a href=#event-offline>offline</a></code> <!-- new -->
<tr><td><dfn id=handler-workerglobalscope-ononline title=handler-WorkerGlobalScope-ononline><code>ononline</code></dfn> <td> <code title=event-online><a href=#event-online>online</a></code> <!-- new -->
</table><h5 id=dedicated-workers-and-the-dedicatedworkerglobalscope-interface><span class=secno>9.2.1.2 </span>Dedicated workers and the <code><a href=#dedicatedworkerglobalscope>DedicatedWorkerGlobalScope</a></code> interface</h5>
@@ -81048,7 +81048,7 @@
scope</var>'s <a href=#dom-workerglobalscope-closing title=dom-WorkerGlobalScope-closing>closing</a> flag is set
to true<!-- v2-onclose and <span title="queue a task">a task is
queued</span> to <span>fire a simple event</span> named <code
- title="event-close">close</code> at <var title="">worker global
+ title="event-worker-close">close</code> at <var title="">worker global
scope</var>-->.</p>
</li>
@@ -81157,7 +81157,7 @@
<p>For each <code>Worker</code> or <code>SharedWorker</code>
object associated with <var title="">worker global scope</var>,
<span>queue a task</span> to <span>fire a simple event</span>
- named <code title="event-close">close</code> at that object.</p>
+ named <code title="event-worker-close">close</code> at that object.</p>
</li>
-->
@@ -81169,7 +81169,7 @@
<li><p>If the worker's <code>WorkerGlobalScope</code> object's
<span title="dom-WorkerGlobalScope-closing">closing</span> flag is
false, <span>queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
worker's <code>WorkerGlobalScope</code> object.</p></li>
--><li><p>Set the worker's <code><a href=#workerglobalscope>WorkerGlobalScope</a></code> object's <a href=#dom-workerglobalscope-closing title=dom-WorkerGlobalScope-closing>closing</a> flag to
true.</li>
@@ -81178,20 +81178,20 @@
<li><p>Wait a user-agent-defined amount of time. If the "<span>run
a worker</span>" processing model defined above immediately starts
running event listeners registered for the <code
- title="event-close">close</code> event, this time should not be
+ title="event-worker-close">close</code> event, this time should not be
zero — the idea is that the <code
- title="event-close">close</code> event can be used to clean up
+ title="event-worker-close">close</code> event can be used to clean up
when shutting down unexpectedly.</p></li>
-->
<li><p>If there are any <a href=#concept-task title=concept-task>tasks</a>
queued in the <a href=#event-loop>event loop</a>'s <a href=#task-queue title="task
queue">task queues</a><!-- v2-onclose other than the <code
- title="event-close">close</code> event that this algorithm just
+ title="event-worker-close">close</code> event that this algorithm just
added-->, discard them without processing them.</li>
<!-- v2-onclose
- <li><p>If the <code title="event-close">close</code> event that
+ <li><p>If the <code title="event-worker-close">close</code> event that
this algorithm just queued hasn't yet been dispatched, then abort
the script currently running in the worker.</p></li>
-->
@@ -81200,7 +81200,7 @@
<li><p>Abort the script currently running in the worker<!--
v2-onclose (if any script is running, then it will be a handler for
- the <code title="event-close">close</code> event)-->.</li>
+ the <code title="event-worker-close">close</code> event)-->.</li>
</ol><p>User agents may invoke the "<a href=#kill-a-worker>kill a worker</a>"
processing model on a worker at any time, e.g. in response to user
@@ -81326,7 +81326,7 @@
<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-abstractworker-onerror title=handler-AbstractWorker-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
-<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
+<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> -->
</table><h5 id=dedicated-workers-and-the-worker-interface><span class=secno>9.2.7.2 </span>Dedicated workers and the <code><a href=#worker>Worker</a></code> interface</h5>
<pre class=idl>[<a href=#dom-worker title=dom-Worker>Constructor</a>(DOMString scriptURL)]
@@ -83136,7 +83136,7 @@
algorithm fails, it triggers the <i><a href=#fail-the-websocket-connection>fail the WebSocket
connection</a></i> algorithm, which then invokes the <i><a href=#close-the-websocket-connection>close the
WebSocket connection</a></i> algorithm, which then establishes that
- <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</li>
@@ -83232,7 +83232,7 @@
<p>Do nothing.</p>
<p class=note>The connection is already closing or is already
- closed. If it has not already, a <code title=event-close>close</code> event will eventually fire <a href=#closeWebSocket>as described below</a>.</p>
+ closed. If it has not already, a <code title=event-socket-close>close</code> event will eventually fire <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83250,7 +83250,7 @@
algorithm invokes the <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> algorithm, which then establishes that
<i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, which fires the
- <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83274,7 +83274,7 @@
<p class=note>The <i><a href=#start-the-websocket-closing-handshake>start the WebSocket closing handshake</a></i>
algorithm eventually invokes the <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> algorithm, which then establishes that <i><a href=#the-websocket-connection-is-closed>the
- WebSocket connection is closed</a></i>, which fires the <code title=event-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
+ WebSocket connection is closed</a></i>, which fires the <code title=event-socket-close>close</code> event <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83290,7 +83290,7 @@
<p class=note><i><a href=#the-websocket-closing-handshake-is-started>The WebSocket closing handshake is
started</a></i>, and will eventually invoke the <i><a href=#close-the-websocket-connection>close the
WebSocket connection</a></i> algorithm, which will establish that
- <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, and thus the <code title=event-close>close</code> event will fire, <a href=#closeWebSocket>as described below</a>.</p>
+ <i><a href=#the-websocket-connection-is-closed>the WebSocket connection is closed</a></i>, and thus the <code title=event-socket-close>close</code> event will fire, <a href=#closeWebSocket>as described below</a>.</p>
</dd>
@@ -83469,7 +83469,7 @@
<tbody><tr><td><dfn id=handler-websocket-onopen title=handler-WebSocket-onopen><code>onopen</code></dfn> <td> <code title=event-open>open</code>
<tr><td><dfn id=handler-websocket-onmessage title=handler-WebSocket-onmessage><code>onmessage</code></dfn> <td> <code title=event-message><a href=#event-message>message</a></code>
<tr><td><dfn id=handler-websocket-onerror title=handler-WebSocket-onerror><code>onerror</code></dfn> <td> <code title=event-error>error</code>
- <tr><td><dfn id=handler-websocket-onclose title=handler-WebSocket-onclose><code>onclose</code></dfn> <td> <code title=event-close>close</code>
+ <tr><td><dfn id=handler-websocket-onclose title=handler-WebSocket-onclose><code>onclose</code></dfn> <td> <code title=event-socket-close>close</code>
</table><h4 id=feedback-from-the-protocol><span class=secno>10.3.3 </span>Feedback from the protocol</h4>
<p>When <i><a href=#the-websocket-connection-is-established>the WebSocket connection is established</a></i>, the user
@@ -83594,7 +83594,7 @@
at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>
<li><p>Create an event that uses the <code><a href=#closeevent>CloseEvent</a></code>
- interface, with the event type <code title=event-close>close</code>, which does not bubble, is not
+ interface, with the event type <code title=event-socket-close>close</code>, which does not bubble, is not
cancelable, has no default action, whose <code title=dom-CloseEvent-wasClean><a href=#dom-closeevent-wasclean>wasClean</a></code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false
otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code>
@@ -83772,18 +83772,18 @@
(0) as of the last time the <a href=#event-loop>event loop</a> started
executing a <a href=#concept-task title=concept-task>task</a> must not be
garbage collected if there are any event listeners registered for
- <code title=event-open>open</code> events, <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code> events, or <code title=event-close>close</code> events.</p>
+ <code title=event-open>open</code> events, <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code> events, or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object whose <code title=dom-WebSocket-readyState><a href=#dom-websocket-readystate>readyState</a></code> attribute's value
was set to <code title=dom-WebSocket-OPEN><a href=#dom-websocket-open>OPEN</a></code> (1) as of
the last time the <a href=#event-loop>event loop</a> started executing a <a href=#concept-task title=concept-task>task</a> must not be garbage collected if
- there are any event listeners registered for <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code>, or <code title=event-close>close</code> events.</p>
+ there are any event listeners registered for <code title=event-message><a href=#event-message>message</a></code> events, <code title=event-error>error</code>, or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object whose <code title=dom-WebSocket-readyState><a href=#dom-websocket-readystate>readyState</a></code> attribute's value
was set to <code title=dom-WebSocket-CLOSING><a href=#dom-websocket-closing>CLOSING</a></code> (2) as
of the last time the <a href=#event-loop>event loop</a> started executing a
<a href=#concept-task title=concept-task>task</a> must not be garbage collected
- if there are any event listeners registered for <code title=event-error>error</code> or <code title=event-close>close</code> events.</p>
+ if there are any event listeners registered for <code title=event-error>error</code> or <code title=event-socket-close>close</code> events.</p>
<p>A <code><a href=#websocket>WebSocket</a></code> object with <i title="the WebSocket
connection is established"><a href=#the-websocket-connection-is-established>an established connection</a></i> that has
@@ -102494,7 +102494,7 @@
<tr><th id=ix-handler-onclose> <code title="">onclose</code>
<td> <a href=#handler-onclose title=handler-onclose>HTML elements</a>
- <td> <code title=event-close>close</code> event handler
+ <td> <code title=event-close><a href=#event-close>close</a></code> event handler
<td> <a href=#event-handler-content-attributes title="event handler content attributes">Event handler content attribute</a>
<tr><th id=ix-handler-oncontextmenu> <code title="">oncontextmenu</code>
Modified: source
===================================================================
--- source 2012-07-27 05:52:36 UTC (rev 7218)
+++ source 2012-07-27 05:56:57 UTC (rev 7219)
@@ -68349,7 +68349,8 @@
</li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at <var
+ event</span> named <dfn
+ title="event-close"><code>close</code></dfn> at <var
title="">dialog</var>.</p></li>
</ol>
@@ -68370,9 +68371,9 @@
<code>Document</code>'s <span>pending dialog stack</span> is not
empty, user agents may provide a user interface that, upon
activation, <span title="queue a task">queues a task</span> to
- <span>fire a simple event</span> named <code
- title="event-cancel">cancel</code> that is cancelable at the top
- <code>dialog</code> element on the <code>Document</code>'s
+ <span>fire a simple event</span> named <dfn
+ title="event-cancel"><code>cancel</code></dfn> that is cancelable at
+ the top <code>dialog</code> element on the <code>Document</code>'s
<span>pending dialog stack</span>. The default action of this event
must be to <span>close the dialog</span> with no return value.</p>
@@ -93774,7 +93775,7 @@
<!-- v2-onclose
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
<code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -93794,7 +93795,7 @@
<thead>
<tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
-<!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
+<!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> -->
<tr><td><dfn title="handler-WorkerGlobalScope-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
<tr><td><dfn title="handler-WorkerGlobalScope-onoffline"><code>onoffline</code></dfn> <td> <code title="event-offline">offline</code> <!-- new -->
<tr><td><dfn title="handler-WorkerGlobalScope-ononline"><code>ononline</code></dfn> <td> <code title="event-online">online</code> <!-- new -->
@@ -94145,7 +94146,7 @@
title="dom-WorkerGlobalScope-closing">closing</span> flag is set
to true<!-- v2-onclose and <span title="queue a task">a task is
queued</span> to <span>fire a simple event</span> named <code
- title="event-close">close</code> at <var title="">worker global
+ title="event-worker-close">close</code> at <var title="">worker global
scope</var>-->.</p>
</li>
@@ -94261,7 +94262,7 @@
<p>For each <code>Worker</code> or <code>SharedWorker</code>
object associated with <var title="">worker global scope</var>,
<span>queue a task</span> to <span>fire a simple event</span>
- named <code title="event-close">close</code> at that object.</p>
+ named <code title="event-worker-close">close</code> at that object.</p>
</li>
-->
@@ -94279,7 +94280,7 @@
<li><p>If the worker's <code>WorkerGlobalScope</code> object's
<span title="dom-WorkerGlobalScope-closing">closing</span> flag is
false, <span>queue a task</span> to <span>fire a simple
- event</span> named <code title="event-close">close</code> at the
+ event</span> named <code title="event-worker-close">close</code> at the
worker's <code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -94291,20 +94292,20 @@
<li><p>Wait a user-agent-defined amount of time. If the "<span>run
a worker</span>" processing model defined above immediately starts
running event listeners registered for the <code
- title="event-close">close</code> event, this time should not be
+ title="event-worker-close">close</code> event, this time should not be
zero — the idea is that the <code
- title="event-close">close</code> event can be used to clean up
+ title="event-worker-close">close</code> event can be used to clean up
when shutting down unexpectedly.</p></li>
-->
<li><p>If there are any <span title="concept-task">tasks</span>
queued in the <span>event loop</span>'s <span title="task
queue">task queues</span><!-- v2-onclose other than the <code
- title="event-close">close</code> event that this algorithm just
+ title="event-worker-close">close</code> event that this algorithm just
added-->, discard them without processing them.</p></li>
<!-- v2-onclose
- <li><p>If the <code title="event-close">close</code> event that
+ <li><p>If the <code title="event-worker-close">close</code> event that
this algorithm just queued hasn't yet been dispatched, then abort
the script currently running in the worker.</p></li>
-->
@@ -94313,7 +94314,7 @@
<li><p>Abort the script currently running in the worker<!--
v2-onclose (if any script is running, then it will be a handler for
- the <code title="event-close">close</code> event)-->.</p></li>
+ the <code title="event-worker-close">close</code> event)-->.</p></li>
</ol>
@@ -94472,7 +94473,7 @@
<tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-AbstractWorker-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
-<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
+<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-worker-close">close</code> -->
</table>
@@ -96593,7 +96594,7 @@
connection</i> algorithm, which then invokes the <i>close the
WebSocket connection</i> algorithm, which then establishes that
<i>the WebSocket connection is closed</i>, which fires the <code
- title="event-close">close</code> event <a
+ title="event-socket-close">close</code> event <a
href="#closeWebSocket">as described below</a>.</p>
</li>
@@ -96715,7 +96716,7 @@
<p class="note">The connection is already closing or is already
closed. If it has not already, a <code
- title="event-close">close</code> event will eventually fire <a
+ title="event-socket-close">close</code> event will eventually fire <a
href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -96736,7 +96737,7 @@
algorithm invokes the <i>close the WebSocket
connection</i> algorithm, which then establishes that
<i>the WebSocket connection is closed</i>, which fires the
- <code title="event-close">close</code> event <a
+ <code title="event-socket-close">close</code> event <a
href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -96769,7 +96770,7 @@
algorithm eventually invokes the <i>close the WebSocket
connection</i> algorithm, which then establishes that <i>the
WebSocket connection is closed</i>, which fires the <code
- title="event-close">close</code> event <a
+ title="event-socket-close">close</code> event <a
href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -96788,7 +96789,7 @@
started</i>, and will eventually invoke the <i>close the
WebSocket connection</i> algorithm, which will establish that
<i>the WebSocket connection is closed</i>, and thus the <code
- title="event-close">close</code> event will fire, <a
+ title="event-socket-close">close</code> event will fire, <a
href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -97010,7 +97011,7 @@
<tr><td><dfn title="handler-WebSocket-onopen"><code>onopen</code></dfn> <td> <code title="event-open">open</code>
<tr><td><dfn title="handler-WebSocket-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
<tr><td><dfn title="handler-WebSocket-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
- <tr><td><dfn title="handler-WebSocket-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code>
+ <tr><td><dfn title="handler-WebSocket-onclose"><code>onclose</code></dfn> <td> <code title="event-socket-close">close</code>
</table>
@@ -97192,7 +97193,7 @@
<li><p>Create an event that uses the <code>CloseEvent</code>
interface, with the event type <code
- title="event-close">close</code>, which does not bubble, is not
+ title="event-socket-close">close</code>, which does not bubble, is not
cancelable, has no default action, whose <code
title="dom-CloseEvent-wasClean">wasClean</code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false
@@ -97404,7 +97405,7 @@
<code title="event-open">open</code> events, <code
title="event-message">message</code> events, <code
title="event-error">error</code> events, or <code
- title="event-close">close</code> events.</p>
+ title="event-socket-close">close</code> events.</p>
<p>A <code>WebSocket</code> object whose <code
title="dom-WebSocket-readyState">readyState</code> attribute's value
@@ -97414,7 +97415,7 @@
there are any event listeners registered for <code
title="event-message">message</code> events, <code
title="event-error">error</code>, or <code
- title="event-close">close</code> events.</p>
+ title="event-socket-close">close</code> events.</p>
<p>A <code>WebSocket</code> object whose <code
title="dom-WebSocket-readyState">readyState</code> attribute's value
@@ -97423,7 +97424,7 @@
<span title="concept-task">task</span> must not be garbage collected
if there are any event listeners registered for <code
title="event-error">error</code> or <code
- title="event-close">close</code> events.</p>
+ title="event-socket-close">close</code> events.</p>
<p>A <code>WebSocket</code> object with <i title="the WebSocket
connection is established">an established connection</i> that has
More information about the Commit-Watchers
mailing list