html5/webstorage Overview.html,1.177,1.178

Update of /sources/public/html5/webstorage
In directory hutz:/tmp/cvs-serv2868

Modified Files:
	Overview.html 
Log Message:
Remove the structed data support from Web Storage. (whatwg r6364)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.177
retrieving revision 1.178
diff -u -d -r1.177 -r1.178
--- Overview.html	28 Jul 2011 01:29:27 -0000	1.177
+++ Overview.html	4 Aug 2011 06:50:52 -0000	1.178
@@ -212,7 +212,7 @@
    <p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72"></a></p>
 
    <h1>Web Storage</h1>
-   <h2 class="no-num no-toc" id="editor-s-draft-28-july-2011">Editor's Draft 28 July 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-4-august-2011">Editor's Draft 4 August 2011</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/webstorage/">http://www.w3.org/TR/webstorage/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -317,7 +317,7 @@
   </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
-  This specification is the 28 July 2011 Editor's Draft.
+  This specification is the 4 August 2011 Editor's Draft.
   </p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
   any patent disclosures</a> made in connection with the deliverables
@@ -382,7 +382,7 @@
    indicate that he wants insurance:</p>
 
    <pre>&lt;label&gt;
- &lt;input type="checkbox" onchange="sessionStorage.insurance = checked"&gt;
+ &lt;input type="checkbox" onchange="sessionStorage.insurance = checked ? 'true' : ''"&gt;
  I want insurance on this trip.
 &lt;/label&gt;</pre>
 
@@ -478,19 +478,14 @@
   widely known. <a href="#refsECMA262">[ECMA262]</a><h2 id="storage"><span class="secno">4 </span>The API</h2><h3 id="the-storage-interface"><span class="secno">4.1 </span>The <code><a href="#storage-0">Storage</a></code> interface</h3><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>;
   DOMString? <a href="#dom-storage-key" title="dom-Storage-key">key</a>(in unsigned long index);
-  getter any <a href="#dom-storage-getitem" title="dom-Storage-getItem">getItem</a>(in DOMString key);
-  setter creator void <a href="#dom-storage-setitem" title="dom-Storage-setItem">setItem</a>(in DOMString key, in any value);
+  getter DOMString <a href="#dom-storage-getitem" title="dom-Storage-getItem">getItem</a>(in DOMString key);
+  setter creator void <a href="#dom-storage-setitem" title="dom-Storage-setItem">setItem</a>(in DOMString key, in DOMString value);
   deleter void <a href="#dom-storage-removeitem" title="dom-Storage-removeItem">removeItem</a>(in DOMString key);
   void <a href="#dom-storage-clear" title="dom-Storage-clear">clear</a>();
 };</pre><p>Each <code><a href="#storage-0">Storage</a></code> object provides access to a list of
   key/value pairs, which are sometimes called items. Keys are
   strings. Any string (including the empty string) is a valid
-  key. Values can be any data type supported by the <span>structured
-  clone</span> algorithm.
-  
-  <a href="#refsHTML">[HTML]</a>
-  
-  <p>Each <code><a href="#storage-0">Storage</a></code> object is associated with a list of
+  key. Values are similarly strings.<p>Each <code><a href="#storage-0">Storage</a></code> object is associated with a list of
   key/value pairs when it is created, as defined in the sections on
   the <code title="dom-sessionStorage"><a href="#dom-sessionstorage">sessionStorage</a></code> and <code title="dom-localStorage"><a href="#dom-localstorage">localStorage</a></code> attributes. Multiple
   separate objects implementing the <code><a href="#storage-0">Storage</a></code> interface can
@@ -505,29 +500,17 @@
   must not.)  If <var title="">n</var> is  greater than or equal to the number of key/value pairs
   in the object, then this method must return null.<p>The <span>supported property names</span> on a
   <code><a href="#storage-0">Storage</a></code> object are the keys of each key/value pair
-  currently present in the list associated with the object.<p>The <dfn id="dom-storage-getitem" title="dom-Storage-getItem"><code>getItem(<var title="">key</var>)</code></dfn> method must return a
-  <span>structured clone</span> of the current value associated with
+  currently present in the list associated with the object.<p>The <dfn id="dom-storage-getitem" title="dom-Storage-getItem"><code>getItem(<var title="">key</var>)</code></dfn> method must return
+  the current value associated with
   the given <var title="">key</var>. If the given <var title="">key</var> does not exist in the list associated with the
   object then this method must return null.
-  
-  <a href="#refsHTML">[HTML]</a>
-  
   <p>The <dfn id="dom-storage-setitem" title="dom-Storage-setItem"><code>setItem(<var title="">key</var>, <var title="">value</var>)</code></dfn> method
-  must first create a <span>structured clone</span> of the given <var title="">value</var>. If this raises an exception, then the
-  exception must be thrown and the list associated with the object is
-  left unchanged. If constructing the stuctured clone would involve
-  constructing a new <code>ImageData</code> object, then throw a
-  <code>NOT_SUPPORTED_ERR</code> exception instead.
-  
-  <a href="#refsHTML">[HTML]</a>
-  
-  </p><p>Otherwise, the user agent must then check if a key/value pair
+  must first check if a key/value pair
   with the given <var title="">key</var> already exists in the list
   associated with the object.<p>If it does not, then a new key/value pair must be added to the
   list, with the given <var title="">key</var> and with its value set
-  to the newly obtained clone of <var title="">value</var>.<p>If the given <var title="">key</var> <em>does</em> exist in the
-  list, then it must have its value updated to the newly obtained
-  clone of <var title="">value</var>.<p>If it couldn't set the new value, the method must raise an
+  to <var title="">value</var>.<p>If the given <var title="">key</var> <em>does</em> exist in the
+  list, then it must have its value updated to <var title="">value</var>.<p>If it couldn't set the new value, the method must raise an
   <code>QUOTA_EXCEEDED_ERR</code> exception. (Setting could fail if,
   e.g., the user has disabled storage for the site, or if the quota
   has been exceeded.)<p>The <dfn id="dom-storage-removeitem" title="dom-Storage-removeItem"><code>removeItem(<var title="">key</var>)</code></dfn> method must cause the key/value
@@ -667,15 +650,11 @@
   becomes <span>fully active</span> again.<p>The <span>task source</span> for this task is the <span>DOM
   manipulation task source</span>.<p>If the event is being fired due to an invocation of the <code title="dom-Storage-setItem"><a href="#dom-storage-setitem">setItem()</a></code> or <code title="dom-Storage-removeItem"><a href="#dom-storage-removeitem">removeItem()</a></code> methods, the
   event must have its <code title="dom-StorageEvent-key"><a href="#dom-storageevent-key">key</a></code>
-  attribute set to the name of the key in question, its <code title="dom-StorageEvent-oldValue"><a href="#dom-storageevent-oldvalue">oldValue</a></code> attribute set to a
-  <span>structured clone</span> of the old value of the key in
-  question, or null if the key is newly added, and its <code title="dom-StorageEvent-newValue"><a href="#dom-storageevent-newvalue">newValue</a></code> attribute set to a
-  <span>structured clone</span> of the new value of the key in
-  question, or null if the key was removed.
-  
-  <a href="#refsHTML">[HTML]</a>
-  
-  <p>Otherwise, if the event is being fired due to an invocation of
+  attribute set to the name of the key in question, its <code title="dom-StorageEvent-oldValue"><a href="#dom-storageevent-oldvalue">oldValue</a></code> attribute set to
+  the old value of the key in question, or null if the key is newly
+  added, and its <code title="dom-StorageEvent-newValue"><a href="#dom-storageevent-newvalue">newValue</a></code> attribute set to
+  the new value of the key in question, or null if the key was
+  removed.<p>Otherwise, if the event is being fired due to an invocation of
   the <code title="dom-Storage-clear"><a href="#dom-storage-clear">clear()</a></code> method, the event
   must have its <code title="dom-StorageEvent-key"><a href="#dom-storageevent-key">key</a></code>, <code title="dom-StorageEvent-oldValue"><a href="#dom-storageevent-oldvalue">oldValue</a></code>, and <code title="dom-StorageEvent-newValue"><a href="#dom-storageevent-newvalue">newValue</a></code> attributes set to
   null.<p>In addition, the event must have its <code title="dom-StorageEvent-url"><a href="#dom-storageevent-url">url</a></code> attribute set to <span title="the document's address">the address of the document</span>
@@ -685,11 +664,11 @@
   kind of <code><a href="#storage-0">Storage</a></code> area as was affected (i.e. session or
   local).<h4 id="event-definition"><span class="secno">4.4.1 </span>Event definition</h4><pre class="idl">interface <dfn id="storageevent">StorageEvent</dfn> : <span>Event</span> {
   readonly attribute DOMString <a href="#dom-storageevent-key" title="dom-StorageEvent-key">key</a>;
-  readonly attribute any <a href="#dom-storageevent-oldvalue" title="dom-StorageEvent-oldValue">oldValue</a>;
-  readonly attribute any <a href="#dom-storageevent-newvalue" title="dom-StorageEvent-newValue">newValue</a>;
+  readonly attribute DOMString? <a href="#dom-storageevent-oldvalue" title="dom-StorageEvent-oldValue">oldValue</a>;
+  readonly attribute DOMString? <a href="#dom-storageevent-newvalue" title="dom-StorageEvent-newValue">newValue</a>;
   readonly attribute DOMString <a href="#dom-storageevent-url" title="dom-StorageEvent-url">url</a>;
   readonly attribute <a href="#storage-0">Storage</a>? <a href="#dom-storageevent-storagearea" title="dom-StorageEvent-storageArea">storageArea</a>;
-  void <a href="#dom-storageevent-initstorageevent" title="dom-StorageEvent-initStorageEvent">initStorageEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString keyArg, in any oldValueArg, in any newValueArg, in DOMString urlArg, in <a href="#storage-0">Storage</a>? storageAreaArg);
+  void <a href="#dom-storageevent-initstorageevent" title="dom-StorageEvent-initStorageEvent">initStorageEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString keyArg, in DOMString? oldValueArg, in DOMString? newValueArg, in DOMString urlArg, in <a href="#storage-0">Storage</a>? storageAreaArg);
 };</pre><p>The <dfn id="dom-storageevent-initstorageevent" title="dom-StorageEvent-initStorageEvent"><code>initStorageEvent()</code></dfn>
   method must initialize the event in a manner analogous to the
   similarly-named method in the DOM Events interfaces. <a href="#refsDOMEVENTS">[DOMEVENTS]</a><p>The <dfn id="dom-storageevent-key" title="dom-StorageEvent-key"><code>key</code></dfn>

Received on Thursday, 4 August 2011 06:51:01 UTC