<div class="gmail_quote">On Tue, Apr 7, 2009 at 5:50 PM, Aryeh Gregor <span dir="ltr"><<a href="mailto:Simetrical%2Bw3c@gmail.com">Simetrical+w3c@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Apr 7, 2009 at 8:24 PM, Brady Eidson <<a href="mailto:beidson@apple.com">beidson@apple.com</a>> wrote:<br>
</div><div class="im">> 1 - Disable LocalStorage completely when private browsing is on. Remove it<br>
> from the DOM completely.<br>
> 2 - Disable LocalStorage mostly when private browsing is on. It exists at<br>
> window.localStorage, but is empty and has a 0-quota.<br>
> 3 - Slide a "fake" LocalStorage object in when private browsing is enabled.<br>
> It starts empty, changes to it are successful, but it is never written to<br>
> disk. When private browsing is disabled, all changes to the private<br>
> browsing proxy are thrown out.<br>
> 4 - Cover the real LocalStorage object with a private browsing layer. It<br>
> starts with all previously stored contents. Any changes to it are pretended<br>
> to occur, but are never written to disk. When private browsing is disabled,<br>
> all items revert to the state they were in when private browsing was enabled<br>
> and writing changes to disk is re-enabled.<br>
> 5 - Treat LocalStorage as read-only when private browsing is on. It exists,<br>
> and all previously stored contents can be retrieved. Any attempt to<br>
> setItem(), removeItem(), or clear() fail.<br>
<br>
</div>How are cookies handled right now? Surely the issues should be pretty<br>
much the same?<br>
<div class="im"></div></blockquote><div><br></div><div>In Chrome, basically like option 3. It's a new profile so it starts with no cookies, cookies can pile up but when the session ends they go away.</div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
> Option 3 is simple to implement and option 4 would difficult to implement<br>
> efficiently. Both would lead to bizarre behavior where data that the<br>
> application thought was saved really wasn't.<br>
<br>
</div>I certainly can't think of how 3 could ever cause a problem. It<br>
should be the same as the user just logging in from a computer they<br>
haven't used before, shouldn't it?<br>
</blockquote><div><br></div><div>yes</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
I'm not certain about 4. What would be a concrete case where 4 would<br>
break, but normal use from multiple computers would not?<br>
<br>
I don't think 1, 2, or 5 are good ideas, since they make localStorage<br>
semi-usable at best when privacy mode is enabled.<br>
</blockquote></div><br>