- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 24 Dec 2008 12:41:31 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv21140 Modified Files: Overview.html Log Message: threads aren't really predictable, but what we want to guarantee can still be required... (credit: pt) (whatwg r2580) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1750 retrieving revision 1.1751 diff -u -d -r1.1750 -r1.1751 --- Overview.html 24 Dec 2008 12:38:02 -0000 1.1750 +++ Overview.html 24 Dec 2008 12:41:28 -0000 1.1751 @@ -31550,8 +31550,8 @@ changed.<p>The <dfn id=dom-storageevent-storagearea title=dom-StorageEvent-storageArea><code>storageArea</code></dfn> attribute represents the <code><a href=#storage-0>Storage</a></code> object that was affected.<h5 id=threads><span class=secno>5.10.1.6 </span>Threads</h5><p>Multiple browsing contexts must be able to access the local - storage areas simultaneously in a predictable manner. Scripts must - not be able to detect any concurrent script execution.<p>This is required to guarantee that the <code title=dom-Storage-length><a href=#dom-storage-length>length</a></code> attribute of a + storage areas simultaneously in such a manner that scripts cannot + detect any concurrent script execution.<p>This is required to guarantee that the <code title=dom-Storage-length><a href=#dom-storage-length>length</a></code> attribute of a <code><a href=#storage-0>Storage</a></code> object never changes while a script is executing, other than in a way that is predictable by the script itself.<p class=note>There are various ways of implementing this
Received on Wednesday, 24 December 2008 12:41:41 UTC