<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 7, 2009, at 6:04 PM, Ian Fette (イアンフェッティ) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">2009/4/7 Jonas Sicking <span dir="ltr"><<a href="mailto:jonas@sicking.cc">jonas@sicking.cc</a>></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"> <br> </div>I do agree that there's still need for storing data while in private<br> browsing mode. So I do think it makes a lot of sense for<br> .sessionStorage to keep working.<br> <br> But I do have concerned about essentially telling a website that we'll<br> store the requested data, only to drop it on the floor as soon as the<br> user exits private browsing mode (or crashes).<br> <font color="#888888"><br> / Jonas<br> </font></blockquote></div><br><div>Doesn't the website have to handle that anyways? I mean, I assume that all the browsers are going to allow users some way to "manage" this stuff, much like cache/cookies - e.g. you have to assume that at some point in time the user is going to blow you away. (Especially on mobile devices where space is more of a premium...)</div></blockquote><div><br></div>Caches are always assumed to be temporary and recoverable, and cookies have severe size and lifetime limitations placed on them (ie - the User Agent can never be excepted to keep cookies around for any predictable lifetime, per the cookies spec).</div><div><br></div><div>LocalStorage and Databases are expected to be persistent unless a script or the user explicitly removes them. They're more like files, where arbitrarily misplacing them is unacceptable.</div><div><br></div><div>~Brady<br><br><blockquote type="cite"><div>-Ian</div></blockquote></div><br></body></html>