- From: Darin Fisher <darin@google.com>
- Date: Sat, 4 Apr 2009 18:10:22 -0700
On Fri, Apr 3, 2009 at 5:29 PM, Ian Hickson <ian at hixie.ch> wrote: > On Fri, 3 Apr 2009, Darin Fisher wrote: > > > > In Chrome we also create a new browsing context when the user types a new > > URL into the location bar of an existing tab. > > So a user can't hit the back button after typing in a URL? The user can, and we then perform that navigation in the previous rendering process or if that process has since been closed, we create a new one for the navigation. We hold all of the state in the main process to facilitate this. > > > The term "browsing context" in the spec basically corresponds to the > session history exposed by window.history, and the outer "Window" object > that the history is on. > > > > 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. > > That's basically what the spec says. OK, that makes sense. -Darin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090404/119adfc2/attachment.htm>
Received on Saturday, 4 April 2009 18:10:22 UTC