W3C home > Mailing lists > Public > public-html-commits@w3.org > January 2011

html5/webstorage Overview.html,1.156,1.157

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Jan 2011 19:57:13 +0000
To: public-html-commits@w3.org
Message-Id: <E1PckLB-0000Dm-Sq@lionel-hutz.w3.org>
Update of /sources/public/html5/webstorage
In directory hutz:/tmp/cvs-serv814

Modified Files:
	Overview.html 
Log Message:
Add references to HTML spec since structured clone is defined there. (whatwg r5770)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -d -r1.156 -r1.157
--- Overview.html	1 Jan 2011 06:34:04 -0000	1.156
+++ Overview.html	11 Jan 2011 19:57:11 -0000	1.157
@@ -229,7 +229,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-1-january-2011">Editor's Draft 1 January 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-11-january-2011">Editor's Draft 11 January 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>
@@ -322,7 +322,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 1 January 2011 Editor's Draft.
+  This specification is the 11 January 2011 Editor's Draft.
   </p><!-- required patent boilerplate --><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
@@ -512,7 +512,11 @@
   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.<p>Each <code><a href="#storage-0">Storage</a></code> object is associated with a list of
+  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/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
@@ -538,12 +542,20 @@
   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
   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.<p>The <dfn id="dom-storage-setitem" title="dom-Storage-setItem"><code>setItem(<var title="">key</var>, <var title="">value</var>)</code></dfn> method
+  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.</p><!-- ImageData isn't supported because reading such objects is
+  <code>NOT_SUPPORTED_ERR</code> exception instead.
+  
+  <a href="#refsHTML">[HTML]</a>
+  
+  </p><!-- ImageData isn't supported because reading such objects is
   synchronous, and getData() is synchronous, and therefore if the
   stored data is in deep storage, it would be very painful to have a
   script grab the value and immediately try to read the image
@@ -697,7 +709,11 @@
   <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.<p>Otherwise, if the event is being fired due to an invocation of
+  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
   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>
Received on Tuesday, 11 January 2011 19:57:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 19:57:19 GMT