- From: poot <cvsmail@w3.org>
- Date: Thu, 1 Apr 2010 14:35:44 +0900 (JST)
- To: public-html-diffs@w3.org
webstorage; hixie: stablise ids for security sections (whatwg r4900)
http://dev.w3.org/cvsweb/html5/webstorage/Overview.html?r1=1.125&r2=1.126&f=h
http://html5.org/tools/web-apps-tracker?from=4899&to=4900
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -d -r1.125 -r1.126
--- Overview.html 4 Mar 2010 07:07:35 -0000 1.125
+++ Overview.html 30 Mar 2010 01:39:38 -0000 1.126
@@ -193,7 +193,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-4-march-2010">Editor's Draft 4 March 2010</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-30-march-2010">Editor's Draft 30 March 2010</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>
@@ -257,7 +257,7 @@
Working Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation track.
- This specification is the 4 March 2010 Editor's Draft.
+ This specification is the 30 March 2010 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
@@ -299,7 +299,7 @@
<ol>
<li><a href="#user-tracking"><span class="secno">6.1 </span>User tracking</a></li>
<li><a href="#sensitivity-of-data"><span class="secno">6.2 </span>Sensitivity of data</a></ol></li>
- <li><a href="#security"><span class="secno">7 </span>Security</a>
+ <li><a href="#security-storage"><span class="secno">7 </span>Security</a>
<ol>
<li><a href="#dns-spoofing-attacks"><span class="secno">7.1 </span>DNS spoofing attacks</a></li>
<li><a href="#cross-directory-attacks"><span class="secno">7.2 </span>Cross-directory attacks</a></li>
@@ -794,7 +794,7 @@
sensitive; it's quite possible for e-mails, calendar appointments,
health records, or other confidential documents to be stored in this
mechanism.<p>To this end, user agents should ensure that when deleting data,
- it is promptly deleted from the underlying storage.<h2 id="security"><span class="secno">7 </span>Security</h2><h3 id="dns-spoofing-attacks"><span class="secno">7.1 </span>DNS spoofing attacks</h3><p>Because of the potential for DNS spoofing attacks, one cannot
+ it is promptly deleted from the underlying storage.<h2 id="security-storage"><span class="secno">7 </span>Security</h2><h3 id="dns-spoofing-attacks"><span class="secno">7.1 </span>DNS spoofing attacks</h3><p>Because of the potential for DNS spoofing attacks, one cannot
guarantee that a host claiming to be in a certain domain really is
from that domain. To mitigate this, pages can use SSL. Pages using
SSL can be sure that only pages using SSL that have certificates
Received on Thursday, 1 April 2010 05:36:31 UTC