[whatwg] Question about "certain cases" for popstate event
paulkinlan at google.com
Wed Jun 1 01:11:26 PDT 2011
Just wanting to ping this thread again.
I am running in to a couple of issues with spec and apparently undefined
1. This case, when does popstate actually fire? We
have inconsistencies in apparent implementation.
2. We have no way to detect onpushstate events
http://paul.kinlan.me/html5-history-needs-another-event so we can't tell
when the URL changes.
3. When combining pushState with AppCache, the urls that are navigated
too via pushState are not added to the application cache groups - and I
think they should.
I am keen to move this forward and would love to work out the best ways.
On Thu, Apr 14, 2011 at 2:56 PM, Rafał Miłecki <zajec5 at gmail.com> wrote:
> W dniu 5 kwietnia 2011 13:03 użytkownik Rafał Miłecki
> <zajec5 at gmail.com> napisał:
> > Hello,
> > There is part of the spec that do not see too obvious for me. Could
> > you help me with that?
> > 18.104.22.168 says:
> >> The popstate event is fired in certain cases when navigating to a
> session history entry.
> > Where can I find definition of that "certain cases"?
> > 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
> > MDC says  event should be fired on *every* change of active history
> >  https://developer.mozilla.org/en/DOM/window.onpopstate
> > ("A popstate event is dispatched to the window every time the active
> > history entry changes.")
> > Which version is correct then?
> Ping? :|
Developer Advocate @ Google for Chrome and HTML5
More information about the whatwg