- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 17 Jun 2011 22:26:08 +0000 (UTC)
On Fri, 17 Jun 2011, Jonas Sicking wrote: > 2011/6/17 Ian Hickson <ian at hixie.ch>: > > On Fri, 17 Jun 2011, Mihai Parparita wrote: > >> On Wed, Jun 15, 2011 at 8:42 PM, Ian Hickson <ian at hixie.ch> wrote: > >> >> Google Chrome 10 seems to fire popstate even if I open totally new > >> >> page. Firefox 4 seems to fire event only on going back/forward > >> > > >> > How are you determining if Firefox fires the event? Are you sure > >> > you're not just checking after Firefox has fired it? > >> > >> Firefox does this intentionally > >> (http://hacks.mozilla.org/2011/03/history-api-changes-in-firefox-4/), > >> and Chrome will be changing to follow suit (http://crbug.com/63040). > >> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12707 is open about this, > >> I'm not sure if there's been any spec changes. > > > > The spec has been updated to match the above, which is why I ask how the > > OP was testing Firefox. The event still fires, it just probably fires > > before any event handlers have been registered. > > Have you really fixed bug 12707? Note that this is not the initial bug > filed on making the spec follow the mozilla proposed changes. If bug > 12707 really has been fixed, it would be great if you could mention > this in the bug and close it. > > [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=12707 Ah, no, hadn't seen that one. Will fix that in due course also. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 17 June 2011 15:26:08 UTC