html5/spec Overview.html,1.1822,1.1823

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv31823

Modified Files:
	Overview.html 
Log Message:
Revamp the DOMStringMap text. (credit: cm) (whatwg r2653)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1822
retrieving revision 1.1823
diff -u -d -r1.1822 -r1.1823
--- Overview.html	13 Jan 2009 09:40:09 -0000	1.1822
+++ Overview.html	13 Jan 2009 10:14:10 -0000	1.1823
@@ -4783,19 +4783,27 @@
 
   </dl><h4 id=domstringmap><span class=secno>2.8.5 </span>DOMStringMap</h4><p>The <code><a href=#domstringmap-0>DOMStringMap</a></code> interface represents a set of
   name-value pairs. When a <code><a href=#domstringmap-0>DOMStringMap</a></code> object is
-  instanced, it is associated with three algorithms, one for getting
-  getting the list of name-value pairs, one for setting names to
-  certain values, and one for deleting names.<pre class=idl>[NameCreator, NameDeleter, NameGetter, NameSetter]
-interface <dfn id=domstringmap-0>DOMStringMap</dfn> {};</pre><p>The <span>names of the supported named properties</span> at any
-  instant are the names obtained from the algorithm for getting the
-  list of name-value pairs at that instant.<p>The value of a property with a name <var title="">name</var> at
-  any instant is the value of the name-value pair with name <var title="">name</var> in the list returned from the algorithm for
-  getting the list of name-value pairs at that instant.<p>The behavior for creating a named property and the behavior for
-  setting a named property are both to invoke the algorithm for
-  setting names to certain values, passing <var title="">name</var> as
-  the name and <var title="">value</var> as the value.<p>The behavior for deleting a named property is to invoke the
-  algorithm for deleting names, passing <var title="">name</var> as
-  the name.<h4 id=dom-feature-strings><span class=secno>2.8.6 </span>DOM feature strings</h4><p>DOM3 Core defines mechanisms for checking for interface support,
+  instantiated, it is associated with three algorithms, one for
+  getting getting the list of name-value pairs, one for setting names
+  to certain values, and one for deleting names.<pre class=idl>[NameCreator, NameDeleter, NameGetter, NameSetter]
+interface <dfn id=domstringmap-0>DOMStringMap</dfn> {};</pre><p>The names of the supported named properties on a
+  <code><a href=#domstringmap-0>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>When a <code><a href=#domstringmap-0>DOMStringMap</a></code> object is indexed to retrieve a
+  named property <var title="">name</var>, the value returned must be
+  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>When a <code><a href=#domstringmap-0>DOMStringMap</a></code> object is indexed to create or
+  modify a named property <var title="">name</var> with 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>When a <code><a href=#domstringmap-0>DOMStringMap</a></code> object is indexed to delete a
+  named property named <var title="">name</var>, the algorithm for
+  deleting names must be run, passing <var title="">name</var> as the
+  name.<p class=note>The <code><a href=#domstringmap-0>DOMStringMap</a></code> interface definition
+  here is only intended for JavaScript environments. Other language
+  bindings will need to define how <code><a href=#domstringmap-0>DOMStringMap</a></code> is to be
+  implemented for those languages.<h4 id=dom-feature-strings><span class=secno>2.8.6 </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=#references>[DOM3CORE]</a><p>A DOM application can use the <dfn id=hasfeature title=hasFeature><code>hasFeature(<var title="">feature</var>,
   <var title="">version</var>)</code></dfn> method of the
@@ -5721,7 +5729,8 @@
   element:<dl><dt>The algorithm for getting the list of name-value pairs</dt>
 
    <dd>
-    <ol><li>Let <var title="">list</var> be an empty list of name-value pairs.</li>
+    <ol><li>Let <var title="">list</var> be an empty list of name-value
+     pairs.</li>
 
      <li>For each content attribute on the element whose first five
      characters are the string "<code title="">data-</code>", add a
@@ -31768,9 +31777,7 @@
 
   </div><p>Each site has its own separate storage area.<p>Storage areas (both session storage and local storage) store
   strings. To store structured data in a storage area, you must first
-  convert it to a string.<h5 id=the-storage-interface><span class=secno>5.10.1.2 </span>The <code><a href=#storage-0>Storage</a></code> interface</h5><!-- XXX shouldn't we define somewhere how null values get handled
-  in these methods? Do they get converted to the empty string or
-  something? --><pre class=idl>interface <dfn id=storage-0>Storage</dfn> {
+  convert it to a string.<h5 id=the-storage-interface><span class=secno>5.10.1.2 </span>The <code><a href=#storage-0>Storage</a></code> interface</h5><pre class=idl>interface <dfn id=storage-0>Storage</dfn> {
   readonly attribute unsigned long <a href=#dom-storage-length title=dom-Storage-length>length</a>;
   [IndexGetter] DOMString <a href=#dom-storage-key title=dom-Storage-key>key</a>(in unsigned long index);
   [NameGetter] DOMString <a href=#dom-storage-getitem title=dom-Storage-getItem>getItem</a>(in DOMString key);

Received on Tuesday, 13 January 2009 10:14:22 UTC