- From: Darin Fisher <darin@chromium.org>
- Date: Mon, 4 Jan 2010 10:54:48 -0800
As follow-up, I've filed these bugs: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8629 https://bugs.webkit.org/show_bug.cgi?id=33160 (Privately, Maciej Stachowiak told me that he supports changing WebKit's pushState implementation to match Firefox, and so I have filed a bug against the spec to get it updated to reflect what implementors are doing.) -Darin <https://bugs.webkit.org/show_bug.cgi?id=33160> 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? > -Darin > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100104/9fed311e/attachment.htm>
Received on Monday, 4 January 2010 10:54:48 UTC