[html5] r7203 - [giow] (0) Four browser vendors have told me they don't want to drop this, so ye [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jul 25 12:11:15 PDT 2012
Author: ianh
Date: 2012-07-25 12:11:14 -0700 (Wed, 25 Jul 2012)
New Revision: 7203
Modified:
complete.html
index
source
Log:
[giow] (0) Four browser vendors have told me they don't want to drop this, so yeah, I'm putting it back. Sorry Anne. :-)
Affected topics: DOM APIs, HTML, WebSocket API
Modified: complete.html
===================================================================
--- complete.html 2012-07-24 18:59:11 UTC (rev 7202)
+++ complete.html 2012-07-25 19:11:14 UTC (rev 7203)
@@ -244,7 +244,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 24 July 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 25 July 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -4031,11 +4031,12 @@
<dd>
- <p>The <dfn id=arraybuffer>ArrayBuffer</dfn> interface and underlying concepts
- from the Typed Array Specification are used for several features
- in this specification. The <dfn id=uint8clampedarray>Uint8ClampedArray</dfn> interface
- type is specifically used in the definition of the
- <code><a href=#the-canvas-element>canvas</a></code> element's 2D API. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+ <p>The <dfn id=arraybuffer>ArrayBuffer</dfn> and <dfn id=arraybufferview>ArrayBufferView</dfn>
+ interfaces and underlying concepts from the Typed Array
+ Specification are used for several features in this specification.
+ The <dfn id=uint8clampedarray>Uint8ClampedArray</dfn> interface type is specifically
+ used in the definition of the <code><a href=#the-canvas-element>canvas</a></code> element's 2D
+ API. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
</dd>
@@ -82938,8 +82939,9 @@
attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-websocket-onmessage title=handler-WebSocket-onmessage>onmessage</a>;
attribute DOMString <a href=#dom-websocket-binarytype title=dom-WebSocket-binaryType>binaryType</a>;
void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(DOMString data);
- void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<span>ArrayBufferView</span> data);
void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#blob>Blob</a> data);
+ void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#arraybuffer>ArrayBuffer</a> data);
+ void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#arraybufferview>ArrayBufferView</a> data);
};</pre>
<p>The <dfn id=dom-websocket title=dom-WebSocket><code>WebSocket(<var title="">url</var>, <var title="">protocols</var>)</code></dfn>
@@ -83309,7 +83311,7 @@
</dd>
- <dt>If the argument is an <code>ArrayBufferView</code> object</dt>
+ <dt>If the argument is an <code><a href=#arraybuffer>ArrayBuffer</a></code> object</dt>
<dd>
@@ -83320,16 +83322,42 @@
buffer is full, the user agent must <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> <a href=#concept-websocket-close-fail title=concept-websocket-close-fail>with
prejudice</a>. The data to be sent is the data stored in the
+ buffer described by the <code><a href=#arraybuffer>ArrayBuffer</a></code> object. <!-- that
+ sentence is meant to invoke "The ArrayBuffer type describes a
+ buffer used to store data for the array buffer views." at the top
+ of the Typed Array spec, and "Optional byteOffset and length can
+ be used to limit the section of the buffer referenced" in the
+ definition of the TypedArray constructor --> Any invocation of
+ this method with an <code><a href=#arraybuffer>ArrayBuffer</a></code> argument that does
+ not throw an exception must increase the <code title=dom-WebSocket-bufferedAmount><a href=#dom-websocket-bufferedamount>bufferedAmount</a></code>
+ attribute by the length of the <code><a href=#arraybuffer>ArrayBuffer</a></code> in bytes.
+ <!-- that sentence is meant to invoke the same as
+ ArrayBuffer.byteLength --> <a href=#refsWSP>[WSP]</a> <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+
+ </dd>
+
+
+ <dt>If the argument is an <code><a href=#arraybufferview>ArrayBufferView</a></code> object</dt>
+
+ <dd>
+
+ <p>If <i><a href=#the-websocket-connection-is-established>the WebSocket connection is established</a></i>, and <i title="the WebSocket closing handshake is started"><a href=#the-websocket-closing-handshake-is-started>the WebSocket
+ closing handshake has not yet started</a></i>, then the user agent
+ must <i>send a WebSocket Message</i> comprised of <var title="">data</var> using a binary frame opcode; if the data
+ cannot be sent, e.g. because it would need to be buffered but the
+ buffer is full, the user agent must <i><a href=#close-the-websocket-connection>close the WebSocket
+ connection</a></i> <a href=#concept-websocket-close-fail title=concept-websocket-close-fail>with
+ prejudice</a>. The data to be sent is the data stored in the
section of the buffer described by the <code><a href=#arraybuffer>ArrayBuffer</a></code>
- object that the <code>ArrayBufferView</code> object references.
+ object that the <code><a href=#arraybufferview>ArrayBufferView</a></code> object references.
<!-- that sentence is meant to invoke "The ArrayBuffer type
describes a buffer used to store data for the array buffer views."
at the top of the Typed Array spec, and "Optional byteOffset and
length can be used to limit the section of the buffer referenced"
in the definition of the TypedArray constructor --> Any invocation
- of this method with an <code>ArrayBufferView</code> argument that
+ of this method with an <code><a href=#arraybufferview>ArrayBufferView</a></code> argument that
does not throw an exception must increase the <code title=dom-WebSocket-bufferedAmount><a href=#dom-websocket-bufferedamount>bufferedAmount</a></code>
- attribute by the length of the <code>ArrayBufferView</code> in
+ attribute by the length of the <code><a href=#arraybufferview>ArrayBufferView</a></code> in
bytes. <!-- that sentence is meant to invoke the same as
ArrayBufferView.byteLength --> <a href=#refsWSP>[WSP]</a> <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
Modified: index
===================================================================
--- index 2012-07-24 18:59:11 UTC (rev 7202)
+++ index 2012-07-25 19:11:14 UTC (rev 7203)
@@ -244,7 +244,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 24 July 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 25 July 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -4031,11 +4031,12 @@
<dd>
- <p>The <dfn id=arraybuffer>ArrayBuffer</dfn> interface and underlying concepts
- from the Typed Array Specification are used for several features
- in this specification. The <dfn id=uint8clampedarray>Uint8ClampedArray</dfn> interface
- type is specifically used in the definition of the
- <code><a href=#the-canvas-element>canvas</a></code> element's 2D API. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+ <p>The <dfn id=arraybuffer>ArrayBuffer</dfn> and <dfn id=arraybufferview>ArrayBufferView</dfn>
+ interfaces and underlying concepts from the Typed Array
+ Specification are used for several features in this specification.
+ The <dfn id=uint8clampedarray>Uint8ClampedArray</dfn> interface type is specifically
+ used in the definition of the <code><a href=#the-canvas-element>canvas</a></code> element's 2D
+ API. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
</dd>
@@ -82938,8 +82939,9 @@
attribute <a href=#eventhandler>EventHandler</a> <a href=#handler-websocket-onmessage title=handler-WebSocket-onmessage>onmessage</a>;
attribute DOMString <a href=#dom-websocket-binarytype title=dom-WebSocket-binaryType>binaryType</a>;
void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(DOMString data);
- void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<span>ArrayBufferView</span> data);
void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#blob>Blob</a> data);
+ void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#arraybuffer>ArrayBuffer</a> data);
+ void <a href=#dom-websocket-send title=dom-WebSocket-send>send</a>(<a href=#arraybufferview>ArrayBufferView</a> data);
};</pre>
<p>The <dfn id=dom-websocket title=dom-WebSocket><code>WebSocket(<var title="">url</var>, <var title="">protocols</var>)</code></dfn>
@@ -83309,7 +83311,7 @@
</dd>
- <dt>If the argument is an <code>ArrayBufferView</code> object</dt>
+ <dt>If the argument is an <code><a href=#arraybuffer>ArrayBuffer</a></code> object</dt>
<dd>
@@ -83320,16 +83322,42 @@
buffer is full, the user agent must <i><a href=#close-the-websocket-connection>close the WebSocket
connection</a></i> <a href=#concept-websocket-close-fail title=concept-websocket-close-fail>with
prejudice</a>. The data to be sent is the data stored in the
+ buffer described by the <code><a href=#arraybuffer>ArrayBuffer</a></code> object. <!-- that
+ sentence is meant to invoke "The ArrayBuffer type describes a
+ buffer used to store data for the array buffer views." at the top
+ of the Typed Array spec, and "Optional byteOffset and length can
+ be used to limit the section of the buffer referenced" in the
+ definition of the TypedArray constructor --> Any invocation of
+ this method with an <code><a href=#arraybuffer>ArrayBuffer</a></code> argument that does
+ not throw an exception must increase the <code title=dom-WebSocket-bufferedAmount><a href=#dom-websocket-bufferedamount>bufferedAmount</a></code>
+ attribute by the length of the <code><a href=#arraybuffer>ArrayBuffer</a></code> in bytes.
+ <!-- that sentence is meant to invoke the same as
+ ArrayBuffer.byteLength --> <a href=#refsWSP>[WSP]</a> <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+
+ </dd>
+
+
+ <dt>If the argument is an <code><a href=#arraybufferview>ArrayBufferView</a></code> object</dt>
+
+ <dd>
+
+ <p>If <i><a href=#the-websocket-connection-is-established>the WebSocket connection is established</a></i>, and <i title="the WebSocket closing handshake is started"><a href=#the-websocket-closing-handshake-is-started>the WebSocket
+ closing handshake has not yet started</a></i>, then the user agent
+ must <i>send a WebSocket Message</i> comprised of <var title="">data</var> using a binary frame opcode; if the data
+ cannot be sent, e.g. because it would need to be buffered but the
+ buffer is full, the user agent must <i><a href=#close-the-websocket-connection>close the WebSocket
+ connection</a></i> <a href=#concept-websocket-close-fail title=concept-websocket-close-fail>with
+ prejudice</a>. The data to be sent is the data stored in the
section of the buffer described by the <code><a href=#arraybuffer>ArrayBuffer</a></code>
- object that the <code>ArrayBufferView</code> object references.
+ object that the <code><a href=#arraybufferview>ArrayBufferView</a></code> object references.
<!-- that sentence is meant to invoke "The ArrayBuffer type
describes a buffer used to store data for the array buffer views."
at the top of the Typed Array spec, and "Optional byteOffset and
length can be used to limit the section of the buffer referenced"
in the definition of the TypedArray constructor --> Any invocation
- of this method with an <code>ArrayBufferView</code> argument that
+ of this method with an <code><a href=#arraybufferview>ArrayBufferView</a></code> argument that
does not throw an exception must increase the <code title=dom-WebSocket-bufferedAmount><a href=#dom-websocket-bufferedamount>bufferedAmount</a></code>
- attribute by the length of the <code>ArrayBufferView</code> in
+ attribute by the length of the <code><a href=#arraybufferview>ArrayBufferView</a></code> in
bytes. <!-- that sentence is meant to invoke the same as
ArrayBufferView.byteLength --> <a href=#refsWSP>[WSP]</a> <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
Modified: source
===================================================================
--- source 2012-07-24 18:59:11 UTC (rev 7202)
+++ source 2012-07-25 19:11:14 UTC (rev 7203)
@@ -20,6 +20,7 @@
interface FileCallback { }; // File API
interface FileList { }; // File API
interface ArrayBuffer { }; // WebGL
+ interface ArrayBufferView { }; // WebGL
interface Uint8ClampedArray { }; // WebGL
interface XMLDocument { }; // DOM Core
interface HTMLCollection { }; // DOM Core
@@ -2988,12 +2989,12 @@
<dd>
- <p>The <dfn>ArrayBuffer</dfn> interface and underlying concepts
- from the Typed Array Specification are used for several features
- in this specification. The <dfn>Uint8ClampedArray</dfn> interface
- type is specifically used in the definition of the
- <code>canvas</code> element's 2D API. <a
- href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
+ <p>The <dfn>ArrayBuffer</dfn> and <dfn>ArrayBufferView</dfn>
+ interfaces and underlying concepts from the Typed Array
+ Specification are used for several features in this specification.
+ The <dfn>Uint8ClampedArray</dfn> interface type is specifically
+ used in the definition of the <code>canvas</code> element's 2D
+ API. <a href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
</dd>
@@ -96382,8 +96383,9 @@
attribute <span>EventHandler</span> <span title="handler-WebSocket-onmessage">onmessage</span>;
attribute DOMString <span title="dom-WebSocket-binaryType">binaryType</span>;
void <span title="dom-WebSocket-send">send</span>(DOMString data);
+ void <span title="dom-WebSocket-send">send</span>(<span>Blob</span> data);
+ void <span title="dom-WebSocket-send">send</span>(<span>ArrayBuffer</span> data);
void <span title="dom-WebSocket-send">send</span>(<span>ArrayBufferView</span> data);
- void <span title="dom-WebSocket-send">send</span>(<span>Blob</span> data);
};</pre>
<p>The <dfn title="dom-WebSocket"><code>WebSocket(<var
@@ -96838,6 +96840,36 @@
</dd>
+ <dt>If the argument is an <code>ArrayBuffer</code> object</dt>
+
+ <dd>
+
+ <p>If <i>the WebSocket connection is established</i>, and <i
+ title="the WebSocket closing handshake is started">the WebSocket
+ closing handshake has not yet started</i>, then the user agent
+ must <i>send a WebSocket Message</i> comprised of <var
+ title="">data</var> using a binary frame opcode; if the data
+ cannot be sent, e.g. because it would need to be buffered but the
+ buffer is full, the user agent must <i>close the WebSocket
+ connection</i> <span title="concept-websocket-close-fail">with
+ prejudice</span>. The data to be sent is the data stored in the
+ buffer described by the <code>ArrayBuffer</code> object. <!-- that
+ sentence is meant to invoke "The ArrayBuffer type describes a
+ buffer used to store data for the array buffer views." at the top
+ of the Typed Array spec, and "Optional byteOffset and length can
+ be used to limit the section of the buffer referenced" in the
+ definition of the TypedArray constructor --> Any invocation of
+ this method with an <code>ArrayBuffer</code> argument that does
+ not throw an exception must increase the <code
+ title="dom-WebSocket-bufferedAmount">bufferedAmount</code>
+ attribute by the length of the <code>ArrayBuffer</code> in bytes.
+ <!-- that sentence is meant to invoke the same as
+ ArrayBuffer.byteLength --> <a href="#refsWSP">[WSP]</a> <a
+ href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
+
+ </dd>
+
+
<dt>If the argument is an <code>ArrayBufferView</code> object</dt>
<dd>
More information about the Commit-Watchers
mailing list