W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2009

[whatwg] Question about pushState

From: Darin Fisher <darin@chromium.org>
Date: Wed, 16 Dec 2009 12:10:40 -0800
Message-ID: <bd8f24d20912161210o5780653dl36fc734f68912421@mail.gmail.com>
On Wed, Dec 16, 2009 at 12: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:
> > [Apologies if this has been discussed before, but I couldn't find it in
> the
> > archives.]
> > Why does pushState only prune forward session history entries
> corresponding
> > to the same document?  I would have expected it to behave like a
> reference
> > fragment navigation, which prunes *all* forward session history entries.
> >  Reason: it seems strange when a "navigation" doesn't result in a
> disabled
> > forward button in the browser UI, so an app developer may be unsatisfied
> > using pushState in place of reference fragment navigations.
> > Thoughts?
>
> I agree. I *think* what you are suggesting is what the implementation
> that Justin Lebar has written for Firefox does.
>
> / Jonas
>


Hmm... the WebKit implementation appears to do as spec'd.

-Darin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091216/a4b287b1/attachment.htm>
Received on Wednesday, 16 December 2009 12:10:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:54 UTC