<div class="gmail_quote">On Wed, Dec 16, 2009 at 12:06 PM, Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher <<a href="mailto:darin@chromium.org">darin@chromium.org</a>> wrote:<br>
> [Apologies if this has been discussed before, but I couldn't find it in the<br>
> archives.]<br>
> Why does pushState only prune forward session history entries corresponding<br>
> to the same document? I would have expected it to behave like a reference<br>
> fragment navigation, which prunes *all* forward session history entries.<br>
> Reason: it seems strange when a "navigation" doesn't result in a disabled<br>
> forward button in the browser UI, so an app developer may be unsatisfied<br>
> using pushState in place of reference fragment navigations.<br>
> Thoughts?<br>
<br>
</div></div>I agree. I *think* what you are suggesting is what the implementation<br>
that Justin Lebar has written for Firefox does.<br>
<font color="#888888"><br>
/ Jonas<br>
</font></blockquote></div><br><div><br></div><div>Hmm... the WebKit implementation appears to do as spec'd.</div><div><br></div><div>-Darin</div>