- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 16 Dec 2009 22:42:20 -0800
On Wed, Dec 16, 2009 at 10:25 PM, Justin Lebar <justin.lebar at gmail.com> wrote: > On Wed, Dec 16, 2009 at 3:06 PM, Jonas Sicking <jonas at sicking.cc> wrote: >> On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher <darin at chromium.org> wrote: >>> I would have expected it to behave like a reference >>> fragment navigation, which prunes *all* forward session history entries. >> >> I agree. I *think* what you are suggesting is what the implementation >> that Justin Lebar has written for Firefox does. > > Yes, with my patch, the forward button is never active after a > pushState. ?It wasn't an intentional deviation from the spec, but I > agree with Darin's reasoning: If pushState is a replacement for the > hash-navigation hack, then it should behave like a hash navigation. I rather think of it as pushState is a way to do AJAX navigation similar to normal navigation. And with normal navigation you loose all your forward history. / Jonas
Received on Wednesday, 16 December 2009 22:42:20 UTC