[whatwg] How long should sessionStorage data persist?
darin at chromium.org
Fri Apr 3 17:03:17 PDT 2009
On Fri, Apr 3, 2009 at 3:16 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Fri, 3 Apr 2009, Jeremy Orlow wrote:
> > I created a page that sets a variable in sessionStorage, then I
> > navigated to a different domain, then I went back to the page and
> > checked if the variable was still set. In Safari 4 (beta) it is. In
> > IE8 it isn't. The spec is not terribly clear: "When a top-level browsing
> > context is destroyed (and therefore permanently inaccessible to the
> > user) the data stored in its session storage areas can be discarded with
> > it, as the API described in this specification provides no way for that
> > data to ever be subsequently retrieved."
> > Can anyone explain what's intended here? If not, can the spec make it
> > more clear?
> IE8 is buggy according to the text you quoted. I don't understand why the
> text is unclear. Does the definition of "browsing context" not leave this
In Chrome we also create a new browsing context when the user types a new
URL into the location bar of an existing tab. This can be thought of as a
shortcut for "create a new tab with the given URL and close the old tab."
(We only do this when the new URL is of a different domain.) Perhaps, IE8 is
doing something similar. Jeremy didn't say how he navigated. A link click or
any content driven navigation cannot be treated like this of course.
However, I believe that we should still restore the old sessionStorage when
the user navigates back to the old URL just as we do for form state, scroll
position, and other attributes normally associated with session history.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg