Short URL: http://html5.org/r/7219
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 7219 | Fix some cross-reference issues. | 2012-07-27 05:56 |
Index: source
===================================================================
--- source (revision 7218)
+++ source (revision 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