<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 31, 2009, at 12:04 PM, Peter Kasting wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Baskerville; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "><div style="word-wrap: break-word; "><div>If you combine that statement with section 6.1's "User agents should present the persistent storage feature to the user in a way that does not distinguish them from HTTP session cookies", then the result is that, when the user requests to delete cookies from a site, the UA will also delete that site's local storage. That is<span class="Apple-converted-space"> </span><i>exactly</i><span class="Apple-converted-space"> </span>the behavior I am concerned about.</div></div></blockquote><div><br></div><div>That's not true. You're misinterpreting a statement about the granularity of control users should have as one about what terminology a UA should use. </div></span></blockquote><div><br></div><div>The [lack of] granularity of control actually is a serious concern, whatever the terminology.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Baskerville; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>The spec already recommends a bunch of things about what users should be shown w.r.t. Local Storage, such as how much space a site is using, so it's clear that a UA that wants to comply with this "should" is going to need to construct UI that doesn't just use the word "cookies" everywhere but actually presents the data as "here's your locally stored data for this site" with local storage content enumerated. Users won't be given a prompt that says "clear cookies" that, confusingly, clears more than cookies; they'll be given a prompt like "clear all locally stored data".</div></span></blockquote><br></div><div>The command will have to say something about cookies or it'll confuse anyone but an HTML5 expert. It'd have to be more like "Clear cookies and other locally stored data".</div><div><br></div><div>The fundamental problem here is that <i>some uses of local storage are nothing at all like cookies</i>, for the same reason that ~/Documents is not the same as ~/Library/Caches. In the example I gave, the user needs to delete cookies for a site, but absolutely should not delete local storage. For the spec to tell browser developers to present the two as being the same thing makes no sense here.</div><div><br></div><div>—Jens</div></body></html>