<div class="gmail_quote">On Fri, Apr 3, 2009 at 5:29 PM, Ian Hickson <span dir="ltr"><ian@hixie.ch></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 Fri, 3 Apr 2009, Darin Fisher wrote:<br>
><br>
> In Chrome we also create a new browsing context when the user types a new<br>
> URL into the location bar of an existing tab.<br>
<br>
</div>So a user can't hit the back button after typing in a URL?</blockquote><div><br></div><div>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.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
The term "browsing context" in the spec basically corresponds to the<br>
session history exposed by window.history, and the outer "Window" object<br>
that the history is on.<br>
<div class="im"><br>
<br>
> However, I believe that we should still restore the old sessionStorage<br>
> when the user navigates back to the old URL just as we do for form<br>
> state, scroll position, and other attributes normally associated with<br>
> session history.<br>
<br>
</div>That's basically what the spec says.</blockquote><div><br></div><div><br></div><div>OK, that makes sense.</div><div><br></div><div>-Darin</div></div>