<div class="gmail_quote">2009/4/7 Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">2009/4/7 Ian Fette ($B%$%"%s%U%'%C%F%#(B) <<a href="mailto:ifette@google.com">ifette@google.com</a>>:<br>
<div class="im">> In Chrome/Chromium, "incognito" mode is basically a new profile that is in<br>
> memory (plus or minus... the cache will never get written out to disk,<br>
> although of course the memory pages could get swapped out and hit the disk<br>
> that way...). The implication is that, for many of these features, things<br>
> could just naturally get handled. That is, whilst the session is active,<br>
> pages can still use a database / local storage / ... / and at the end of the<br>
> session, when that profile is deleted, things will go away. I personally<br>
> like that approach, as there may be legitimate reasons to want to use a<br>
> database even for just a single session. (Perhaps someone wants to edit a<br>
> spreadsheet and the spreadsheet app wants to use a database on the client as<br>
> a backing store for fast edits, I don't know...). I just don't like the idea<br>
> of saying "Sorry, incognito/private/... means a class of pages won't work"<br>
> if there's no reason it has to be that way.<br>
> In short, I would prefer something closest to Option 3. It lets pages just<br>
> work, but respects the privacy wishes of the user. (AppCache / persistent<br>
> workers are the one exception where I think Option3 doesn't apply and we<br>
> need to figure something out.)<br>
<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>
<div><br></div><div>-Ian</div>