- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Jul 2011 07:23:18 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv11858
Modified Files:
Overview.html
Log Message:
moving sections around (whatwg r6319)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5049
retrieving revision 1.5050
diff -u -d -r1.5049 -r1.5050
--- Overview.html 22 Jul 2011 07:01:47 -0000 1.5049
+++ Overview.html 22 Jul 2011 07:23:14 -0000 1.5050
@@ -569,9 +569,9 @@
<li><a href="#htmloptionscollection-0"><span class="secno">2.8.2.4 </span>HTMLOptionsCollection</a></ol></li>
<li><a href="#domtokenlist-0"><span class="secno">2.8.3 </span>DOMTokenList</a></li>
<li><a href="#domsettabletokenlist-0"><span class="secno">2.8.4 </span>DOMSettableTokenList</a></li>
- <li><a href="#transferable-objects"><span class="secno">2.8.5 </span>Transferable objects</a></li>
- <li><a href="#safe-passing-of-structured-data"><span class="secno">2.8.6 </span>Safe passing of structured data</a></li>
- <li><a href="#domstringmap-0"><span class="secno">2.8.7 </span>DOMStringMap</a></li>
+ <li><a href="#domstringmap-0"><span class="secno">2.8.5 </span>DOMStringMap</a></li>
+ <li><a href="#transferable-objects"><span class="secno">2.8.6 </span>Transferable objects</a></li>
+ <li><a href="#safe-passing-of-structured-data"><span class="secno">2.8.7 </span>Safe passing of structured data</a></li>
<li><a href="#dom-feature-strings"><span class="secno">2.8.8 </span>DOM feature strings</a></li>
<li><a href="#exceptions"><span class="secno">2.8.9 </span>Exceptions</a></li>
<li><a href="#garbage-collection"><span class="secno">2.8.10 </span>Garbage collection</a></ol></li>
@@ -7265,7 +7265,81 @@
attribute must return the underlying string on getting, and must
replace the underlying string with the new value on setting.</p>
- </div><h4 id="transferable-objects"><span class="secno">2.8.5 </span>Transferable objects</h4><p>Some objects support being copied and closed in one operation.
+ </div><h4 id="domstringmap-0"><span class="secno">2.8.5 </span>DOMStringMap</h4><p>The <code><a href="#domstringmap">DOMStringMap</a></code> interface represents a set of
+ name-value pairs. It exposes these using the scripting language's
+ native mechanisms for property access.<div class="impl">
+
+ <p>When a <code><a href="#domstringmap">DOMStringMap</a></code> object is instantiated, it is
+ associated with three algorithms, one for getting the list of
+ name-value pairs, one for setting names to certain values, and one
+ for deleting names.</p>
+
+ <pre class="idl">interface <dfn id="domstringmap">DOMStringMap</dfn> {
+ <a href="#dom-domstringmap-nameditem" title="dom-DOMStringMap-namedItem">getter</a> DOMString (in DOMString name);
+ <a href="#dom-domstringmap-setitem" title="dom-DOMStringMap-setItem">setter</a> void (in DOMString name, in DOMString value);
+ <a href="#dom-domstringmap-additem" title="dom-DOMStringMap-addItem">creator</a> void (in DOMString name, in DOMString value);
+ <a href="#dom-domstringmap-removeitem" title="dom-DOMStringMap-removeItem">deleter</a> void (in DOMString name);
+};</pre>
+
+ <p>The <a href="#supported-property-names">supported property names</a> on a
+ <code><a href="#domstringmap">DOMStringMap</a></code> object at any instant are the names of
+ each pair returned from the algorithm for getting the list of
+ name-value pairs at that instant.</p>
+
+ <p>To <dfn id="dom-domstringmap-nameditem" title="dom-DOMStringMap-namedItem">determine the value of
+ a named property</dfn> <var title="">name</var> in a
+ <code><a href="#domstringmap">DOMStringMap</a></code>, the user agent must return the value
+ component of the name-value pair whose name component is <var title="">name</var> in the list returned by the algorithm for
+ getting the list of name-value pairs.</p>
+
+ <p>To set the value of a <dfn id="dom-domstringmap-additem" title="dom-DOMStringMap-addItem">new</dfn> or <dfn id="dom-domstringmap-setitem" title="dom-DOMStringMap-setItem">existing</dfn> named property <var title="">name</var> to value <var title="">value</var>, the
+ algorithm for setting names to certain values must be run, passing
+ <var title="">name</var> as the name and the result of converting
+ <var title="">value</var> to a <code>DOMString</code> as the
+ value.</p>
+
+ <p>To <dfn id="dom-domstringmap-removeitem" title="dom-DOMStringMap-removeItem">delete an existing
+ named property</dfn> <var title="">name</var>, the algorithm for
+ deleting names must be run, passing <var title="">name</var> as the
+ name.</p>
+
+ <p class="note">The <code><a href="#domstringmap">DOMStringMap</a></code> interface definition
+ here is only intended for JavaScript environments. Other language
+ bindings will need to define how <code><a href="#domstringmap">DOMStringMap</a></code> is to be
+ implemented for those languages.</p>
+
+ </div><div class="example">
+
+ <p>The <code title="dom-dataset"><a href="#dom-dataset">dataset</a></code> attribute on
+ elements exposes the <code title="attr-data-*"><a href="#attr-data">data-*</a></code>
+ attributes on the element.</p>
+
+ <p>Given the following fragment and elements with similar
+ constructions:</p>
+
+ <pre><img class="tower" id="tower5" data-x="12" data-y="5"
+ data-ai="robotarget" data-hp="46" data-ability="flames"
+ src="towers/rocket.png alt="Rocket Tower"></pre>
+
+ <p>...one could imagine a function <code title="">splashDamage()</code> that takes some arguments, the first
+ of which is the element to process:</p>
+
+ <pre>function splashDamage(node, x, y, damage) {
+ if (node.classList.contains('tower') && // checking the 'class' attribute
+ node.dataset.x == x && // reading the 'data-x' attribute
+ node.dataset.y == y) { // reading the 'data-y' attribute
+ var hp = parseInt(node.dataset.hp); // reading the 'data-hp' attribute
+ hp = hp - damage;
+ if (hp < 0) {
+ hp = 0;
+ node.dataset.ai = 'dead'; // setting the 'data-ai' attribute
+ delete node.dataset.ability; // removing the 'data-ability' attribute
+ }
+ node.dataset.hp = hp; // setting the 'data-hp' attribute
+ }
+}</pre>
+
+ </div><h4 id="transferable-objects"><span class="secno">2.8.6 </span>Transferable objects</h4><p>Some objects support being copied and closed in one operation.
This is called <i>transferring</i> the object, and is used in
particular to transfer ownership of unsharable or expensive
resources across worker boundaries.<pre class="idl">[NoInterfaceObject]
@@ -7282,7 +7356,7 @@
</ul><div class="impl">
- <h4 id="safe-passing-of-structured-data"><span class="secno">2.8.6 </span>Safe passing of structured data</h4>
+ <h4 id="safe-passing-of-structured-data"><span class="secno">2.8.7 </span>Safe passing of structured data</h4>
<p>When a user agent is required to obtain a <dfn id="structured-clone">structured
clone</dfn> of a value, optionally with a <i>transfer map</i>, it
@@ -7450,80 +7524,6 @@
</ol><p class="note">This algorithm preserves cycles and preserves the
identity of duplicate objects in graphs.</p>
- </div><h4 id="domstringmap-0"><span class="secno">2.8.7 </span>DOMStringMap</h4><p>The <code><a href="#domstringmap">DOMStringMap</a></code> interface represents a set of
- name-value pairs. It exposes these using the scripting language's
- native mechanisms for property access.<div class="impl">
-
- <p>When a <code><a href="#domstringmap">DOMStringMap</a></code> object is instantiated, it is
- associated with three algorithms, one for getting the list of
- name-value pairs, one for setting names to certain values, and one
- for deleting names.</p>
-
- <pre class="idl">interface <dfn id="domstringmap">DOMStringMap</dfn> {
- <a href="#dom-domstringmap-nameditem" title="dom-DOMStringMap-namedItem">getter</a> DOMString (in DOMString name);
- <a href="#dom-domstringmap-setitem" title="dom-DOMStringMap-setItem">setter</a> void (in DOMString name, in DOMString value);
- <a href="#dom-domstringmap-additem" title="dom-DOMStringMap-addItem">creator</a> void (in DOMString name, in DOMString value);
- <a href="#dom-domstringmap-removeitem" title="dom-DOMStringMap-removeItem">deleter</a> void (in DOMString name);
-};</pre>
-
- <p>The <a href="#supported-property-names">supported property names</a> on a
- <code><a href="#domstringmap">DOMStringMap</a></code> object at any instant are the names of
- each pair returned from the algorithm for getting the list of
- name-value pairs at that instant.</p>
-
- <p>To <dfn id="dom-domstringmap-nameditem" title="dom-DOMStringMap-namedItem">determine the value of
- a named property</dfn> <var title="">name</var> in a
- <code><a href="#domstringmap">DOMStringMap</a></code>, the user agent must return the value
- component of the name-value pair whose name component is <var title="">name</var> in the list returned by the algorithm for
- getting the list of name-value pairs.</p>
-
- <p>To set the value of a <dfn id="dom-domstringmap-additem" title="dom-DOMStringMap-addItem">new</dfn> or <dfn id="dom-domstringmap-setitem" title="dom-DOMStringMap-setItem">existing</dfn> named property <var title="">name</var> to value <var title="">value</var>, the
- algorithm for setting names to certain values must be run, passing
- <var title="">name</var> as the name and the result of converting
- <var title="">value</var> to a <code>DOMString</code> as the
- value.</p>
-
- <p>To <dfn id="dom-domstringmap-removeitem" title="dom-DOMStringMap-removeItem">delete an existing
- named property</dfn> <var title="">name</var>, the algorithm for
- deleting names must be run, passing <var title="">name</var> as the
- name.</p>
-
- <p class="note">The <code><a href="#domstringmap">DOMStringMap</a></code> interface definition
- here is only intended for JavaScript environments. Other language
- bindings will need to define how <code><a href="#domstringmap">DOMStringMap</a></code> is to be
- implemented for those languages.</p>
-
- </div><div class="example">
-
- <p>The <code title="dom-dataset"><a href="#dom-dataset">dataset</a></code> attribute on
- elements exposes the <code title="attr-data-*"><a href="#attr-data">data-*</a></code>
- attributes on the element.</p>
-
- <p>Given the following fragment and elements with similar
- constructions:</p>
-
- <pre><img class="tower" id="tower5" data-x="12" data-y="5"
- data-ai="robotarget" data-hp="46" data-ability="flames"
- src="towers/rocket.png alt="Rocket Tower"></pre>
-
- <p>...one could imagine a function <code title="">splashDamage()</code> that takes some arguments, the first
- of which is the element to process:</p>
-
- <pre>function splashDamage(node, x, y, damage) {
- if (node.classList.contains('tower') && // checking the 'class' attribute
- node.dataset.x == x && // reading the 'data-x' attribute
- node.dataset.y == y) { // reading the 'data-y' attribute
- var hp = parseInt(node.dataset.hp); // reading the 'data-hp' attribute
- hp = hp - damage;
- if (hp < 0) {
- hp = 0;
- node.dataset.ai = 'dead'; // setting the 'data-ai' attribute
- delete node.dataset.ability; // removing the 'data-ability' attribute
- }
- node.dataset.hp = hp; // setting the 'data-hp' attribute
- }
-}</pre>
-
</div><h4 id="dom-feature-strings"><span class="secno">2.8.8 </span>DOM feature strings</h4><p>DOM3 Core defines mechanisms for checking for interface support,
and for obtaining implementations of interfaces, using <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures">feature
strings</a>. <a href="#refsDOMCORE">[DOMCORE]</a><p>Authors are strongly discouraged from using these, as they are
Received on Friday, 22 July 2011 07:23:19 UTC