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
[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
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@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
On Wed, Dec 16, 2009 at 12:06 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@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
Jonas Sicking wrote:
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@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
On Wed, Dec 16, 2009 at 3:06 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@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
On Wed, Dec 16, 2009 at 10:25 PM, Justin Lebar justin.le...@gmail.com wrote:
On Wed, Dec 16, 2009 at 3:06 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Dec 16, 2009 at 11:51 AM, Darin Fisher da...@chromium.org wrote:
I would have expected it to behave like a reference
fragment navigation,