- From: Henry Chan <henry.fai.hang.chan@gmail.com>
- Date: Fri, 24 Dec 2010 10:18:40 +0800
It fixes the bit where back/forward before onload doesn't fire onpopstate. But no, it still doesn't let us detect inital onpopstate. And back/forward buttons don't work properly until onload. A workaround would be to assign the handlers to the <a> tags at onload but again that's not feasible for my site. I need it domready. Please make onpopstate fire as early as possible in the navigation sequence. And drop the pending state object. I need exactly each firing. Not just the last one. On Mon, Dec 20, 2010 at 8:28 PM, Anne van Kesteren <annevk at opera.com> wrote: > On Sun, 19 Dec 2010 08:42:09 +0100, Henry Chan < > henry.fai.hang.chan at gmail.com> wrote: > >> *bump* >> >> This is really serious, it blocks a very good use of the API, and it's >> unreliable to use it if back and forward is clicekd before onload. >> > > This got fixed, no? > > http://html5.org/tools/web-apps-tracker?from=5685&to=5686 > > > -- > Anne van Kesteren > http://annevankesteren.nl/ > -- Henry Chan henry.fai.hang.chan at gmail.com Administrator of www.123got-it.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20101224/f272be90/attachment.htm>
Received on Thursday, 23 December 2010 18:18:40 UTC