[whatwg] Question about "certain cases" for popstate event

Just wanting to ping this thread again.

I am running in to a couple of issues with spec and apparently undefined
cases:

   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.

P

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?
> >
> > 6.5.9.1 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 [1] event should be fired on *every* change of active history
> entry
> >
> > [1] 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? :|
>
> --
> Rafa?
>



-- 
Paul Kinlan
Developer Advocate @ Google for Chrome and HTML5
t: +447730517944
tw: @Paul_Kinlan
LinkedIn: http://uk.linkedin.com/in/paulkinlan
Blog: http://paul.kinlan.me
Skype: paul.kinlan

Received on Wednesday, 1 June 2011 01:11:26 UTC