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

[whatwg] Question about pushState

From: Jonathan 'J5' Cook <jonathan.j5.cook@gmail.com>
Date: Wed, 16 Dec 2009 15:52:05 -0500
Message-ID: <4B294875.3070505@gmail.com>
Jonas Sicking 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
I would think that the behavior has to do with the definition of URL/URI 
and URL/URI fragment.  Moving backwards inside a page is considered 
navigation inside the URL/document (think scrolling in a page that is 
not enhanced), AFAICT.

Received on Wednesday, 16 December 2009 12:52:05 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:19 UTC