[html5] r6537 - [e] (0) mention typedarray for xref
whatwg at whatwg.org
whatwg at whatwg.org
Sun Sep 4 10:57:41 PDT 2011
Author: ianh
Date: 2011-09-04 10:57:39 -0700 (Sun, 04 Sep 2011)
New Revision: 6537
Modified:
complete.html
index
source
Log:
[e] (0) mention typedarray for xref
Modified: complete.html
===================================================================
--- complete.html 2011-09-04 17:52:59 UTC (rev 6536)
+++ complete.html 2011-09-04 17:57:39 UTC (rev 6537)
@@ -3916,6 +3916,16 @@
</dd>
+ <dt>Typed Arrays</dt>
+
+ <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. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+
+ </dd>
+
<dt>JavaScript</dt>
<dd>
@@ -77806,7 +77816,7 @@
<p>To <em>send</em> data to a worker, use the <code title=dom-Worker-postMessage><a href=#dom-worker-postmessage>postMessage()</a></code> method.
Structured data can be sent over this communication channel. To send
- <code>ArrayBuffer</code> objects efficiently (by transferring them
+ <code><a href=#arraybuffer>ArrayBuffer</a></code> objects efficiently (by transferring them
rather than cloning them), list them in an array in the second
argument.</p>
@@ -80060,7 +80070,7 @@
attribute <a href=#function>Function</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>ArrayBuffer</span> 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=#blob>Blob</a> data);
};</pre>
@@ -80353,7 +80363,7 @@
<p class=note>This attribute allows authors to control how binary
data is exposed to scripts. By setting the attribute to "<code title="">blob</code>", binary data is returned in <code><a href=#blob>Blob</a></code>
form; by setting it to "<code title="">arraybuffer</code>", it is
- returned in <code>ArrayBuffer</code> form. User agents can use this
+ returned in <code><a href=#arraybuffer>ArrayBuffer</a></code> form. User agents can use this
as a hint for how to handle incoming binary data: if the attribute
is set to "<code title="">blob</code>", it is safe to spool it to
disk, and if it is set to "<code title="">arraybuffer</code>", it is
@@ -80417,7 +80427,7 @@
</dd>
- <dt>If the argument is an <code>ArrayBuffer</code> object</dt>
+ <dt>If the argument is an <code><a href=#arraybuffer>ArrayBuffer</a></code> object</dt>
<dd>
@@ -80428,13 +80438,13 @@
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>ArrayBuffer</code> object. <!-- that
+ 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 --> Any invokation of this method with an
- <code>ArrayBuffer</code> argument that does not raise an exception
+ <code><a href=#arraybuffer>ArrayBuffer</a></code> argument that does not raise 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>ArrayBuffer</code> in bytes.
+ 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>
@@ -80510,7 +80520,7 @@
<p>If <var title="">type</var> indicates that the data is Binary,
and <code title=dom-WebSocket-binaryType><a href=#dom-websocket-binarytype>binaryType</a></code> is
set to "<code title="">arraybuffer</code>", then set <var title="">event</var>'s <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute to a new
- read-only <code>ArrayBuffer</code> object whose contents are <var title="">data</var>. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+ read-only <code><a href=#arraybuffer>ArrayBuffer</a></code> object whose contents are <var title="">data</var>. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
</li>
@@ -80530,7 +80540,7 @@
above <a href=#concept-task title=concept-task>task</a> for this particular
message the script switched <code title=dom-WebSocket-binaryType><a href=#dom-websocket-binarytype>binaryType</a></code> to "<code title="">arraybuffer</code>", the user agent would want to page the
data back to RAM before running this <a href=#concept-task title=concept-task>task</a> so as to avoid stalling the main
- thread while it created the <code>ArrayBuffer</code> object.</p>
+ thread while it created the <code><a href=#arraybuffer>ArrayBuffer</a></code> object.</p>
<hr><p>When <i><a href=#the-websocket-closing-handshake-is-started>the WebSocket closing handshake is started</a></i>, the user
agent must <a href=#queue-a-task>queue a task</a> to change the <code title=dom-WebSocket-readyState><a href=#dom-websocket-readystate>readyState</a></code> attribute's value
Modified: index
===================================================================
--- index 2011-09-04 17:52:59 UTC (rev 6536)
+++ index 2011-09-04 17:57:39 UTC (rev 6537)
@@ -3813,6 +3813,16 @@
</dd>
+ <dt>Typed Arrays</dt>
+
+ <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. <a href=#refsTYPEDARRAY>[TYPEDARRAY]</a></p>
+
+ </dd>
+
<dt>JavaScript</dt>
<dd>
@@ -96364,6 +96374,9 @@
<dt id=refsTURN>[TURN]</dt>
<dd><cite><a href=http://tools.ietf.org/html/rfc5766>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)</a></cite>, R. Mahy, P. Matthews, J. Rosenberg. IETF.</dd>
+ <dt id=refsTYPEDARRAY>[TYPEDARRAY]</dt>
+ <dd><cite><a href=http://www.khronos.org/registry/typedarray/specs/latest/>Typed Array Specification</a></cite>, D. Herman, K. Russell. Khronos.</dd>
+
<dt id=refsUAAG>[UAAG]</dt>
<dd>(Non-normative) <cite><a href=http://www.w3.org/TR/UAAG20/>Web Content Accessibility
Guidelines (UAAG) 2.0</a></cite>, J. Allan, K. Ford, J. Richards,
Modified: source
===================================================================
--- source 2011-09-04 17:52:59 UTC (rev 6536)
+++ source 2011-09-04 17:57:39 UTC (rev 6537)
@@ -2846,6 +2846,17 @@
</dd>
+ <dt>Typed Arrays</dt>
+
+ <dd>
+
+ <p>The <dfn>ArrayBuffer</dfn> interface and underlying concepts
+ from the Typed Array Specification are used for several features
+ in this specification. <a
+ href="#refsTYPEDARRAY">[TYPEDARRAY]</a></p>
+
+ </dd>
+
<dt>JavaScript</dt>
<dd>
More information about the Commit-Watchers
mailing list