[html5] r7399 - [e] (0) Fix the intro to be more accurate about what the feature provides Fixing [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Sep 24 20:41:05 PDT 2012
Author: ianh
Date: 2012-09-24 20:41:03 -0700 (Mon, 24 Sep 2012)
New Revision: 7399
Modified:
complete.html
index
source
Log:
[e] (0) Fix the intro to be more accurate about what the feature provides
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=16198
Affected topics: DOM APIs, Web Storage
Modified: complete.html
===================================================================
--- complete.html 2012-09-25 03:31:03 UTC (rev 7398)
+++ complete.html 2012-09-25 03:41:03 UTC (rev 7399)
@@ -86809,7 +86809,6 @@
</div><!--data-component-->
-<!--POSTMSG-->
@@ -86825,9 +86824,8 @@
<p><i>This section is non-normative.</i></p>
- <p>This specification introduces two related mechanisms, similar to
- HTTP session cookies, for storing structured data on the client
- side. <a href=#refsCOOKIES>[COOKIES]</a></p>
+ <p>This specification introduces two related mechanisms, similar to HTTP session cookies, for
+ storing name-value pairs on the client side. <a href=#refsCOOKIES>[COOKIES]</a></p>
<p>The first is designed for scenarios where the user is carrying
out a single transaction, but could be carrying out multiple
Modified: index
===================================================================
--- index 2012-09-25 03:31:03 UTC (rev 7398)
+++ index 2012-09-25 03:41:03 UTC (rev 7399)
@@ -86809,7 +86809,6 @@
</div><!--data-component-->
-<!--POSTMSG-->
@@ -86825,9 +86824,8 @@
<p><i>This section is non-normative.</i></p>
- <p>This specification introduces two related mechanisms, similar to
- HTTP session cookies, for storing structured data on the client
- side. <a href=#refsCOOKIES>[COOKIES]</a></p>
+ <p>This specification introduces two related mechanisms, similar to HTTP session cookies, for
+ storing name-value pairs on the client side. <a href=#refsCOOKIES>[COOKIES]</a></p>
<p>The first is designed for scenarios where the user is carrying
out a single transaction, but could be carrying out multiple
Modified: source
===================================================================
--- source 2012-09-25 03:31:03 UTC (rev 7398)
+++ source 2012-09-25 03:41:03 UTC (rev 7399)
@@ -100815,8 +100815,7 @@
</div><!--data-component-->
-<!--START w3c-html--><!--POSTMSG-->
-<!--END dev-html--><!--END w3c-html-->
+<!--END dev-html-->
@@ -100832,9 +100831,8 @@
<!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
- <p>This specification introduces two related mechanisms, similar to
- HTTP session cookies, for storing structured data on the client
- side. <a href="#refsCOOKIES">[COOKIES]</a></p>
+ <p>This specification introduces two related mechanisms, similar to HTTP session cookies, for
+ storing name-value pairs on the client side. <a href="#refsCOOKIES">[COOKIES]</a></p>
<p>The first is designed for scenarios where the user is carrying
out a single transaction, but could be carrying out multiple
More information about the Commit-Watchers
mailing list