spec/Overview.html 1.1030 1841 xref typos (whatwg r1841) (changed by: I

xref typos (whatwg r1841) (changed by: Ian Hickson)

Diffs for this change per section: 
  http://people.w3.org/mike/diffs/html5/spec/Overview.1.1030.html#fire-a
  http://people.w3.org/mike/diffs/html5/spec/Overview.1.1030.html#disconnect

Current content per affected section: 
  http://dev.w3.org/html5/spec/Overview.html#fire-a
  http://dev.w3.org/html5/spec/Overview.html#disconnect

Previously published WD content per affected section: 
  http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#fire-a
  http://www.w3.org/TR/2008/WD-html5-20080610/single-page/#disconnect

Cumulative diff: http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1029&r2=1.1030&f=h

http://html5.org/tools/web-apps-tracker?from=1840&to=1841

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1029
retrieving revision 1.1030
diff -u -d -r1.1029 -r1.1030
--- Overview.html	3 Jul 2008 08:36:43 -0000	1.1029
+++ Overview.html	3 Jul 2008 09:01:54 -0000	1.1030
@@ -41453,8 +41453,8 @@
    title=dom-WebSocket-disconnect><code>disconnect()</code></dfn> method must
    <a href="#close1">close the Web Socket connection</a> or connection
    attempt, if any. If the connection is already closed, it must do nothing.
-   Closing the connection causes a <code
-   title=event-connection-close>close</code> event to be fired and the <code
+   Closing the connection causes a <code title=event-WebSocket-close><a
+   href="#close0">close</a></code> event to be fired and the <code
    title=dom-WebSocket-readyState><a
    href="#readystate1">readyState</a></code> attribute's value to change, as
    <a href="#closeWebSocket">described below</a>.
@@ -41513,9 +41513,9 @@
    <code><a href="#websocket0">WebSocket</a></code> object being created
    &mdash; and thus the connection being established &mdash; and the current
    script completing; or, during the execution of a <code
-   title=event-connection-read>read</code> event handler) must be buffered,
-   and those events queued up and each one individually fired after the
-   script has completed.</p>
+   title=event-WebSocket-read><a href="#read">read</a></code> event handler)
+   must be buffered, and those events queued up and each one individually
+   fired after the script has completed.</p>
   <!-- XXX make this more generic
   -->

Received on Thursday, 3 July 2008 09:05:10 UTC