<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - QuotaExceededError when saving to localStorage in private mode - leaks users browsing preference"
href="https://bugs.webkit.org/show_bug.cgi?id=157010#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - QuotaExceededError when saving to localStorage in private mode - leaks users browsing preference"
href="https://bugs.webkit.org/show_bug.cgi?id=157010">bug 157010</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=157010#c7">comment #7</a>)
<span class="quote">> Also, re:permanent storage. From the page author's point of view, they can
> only judge permanence of storage per user, which they can alternatively
> track via cookies. So, resetting localStorage when cookies are reset (as
> when they close private mode) makes sense.</span >
We thought about this very carefully when we implemented localStorage for the browser before anybody but the Gears plugin
Cookies are a completely different class of storage from localStorage.
Browsers are allowed to make all cookies session cookies, ditch cookies in FIFO order to make room for new ones, ditch big cookies first, ditch cookies in any arbitrary order, decide not to store a cookie "just because it looks weird", etc etc, and still match the spirit of the spec.
LocalStorage was meant to be durable.
All of this said, it's a shame that none of the other browsers considered this the same way.
Note, I'm not *defending* how our behavior reveals private browsing state. Of course that's terrible.
I am lamenting that nobody worked together to try to come up with something better.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>