- From: <bugzilla@jessica.w3.org>
- Date: Tue, 14 Dec 2010 06:16:36 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11468 --- Comment #4 from henry.fai.hang.chan@gmail.com 2010-12-14 06:16:35 UTC --- > The pending state object is used to keep track of what state object to use in > the inital popstate event fired by the parser once it stops parsing. The pending > state object must be initially null. Why do we need a pending state object? It's useless. If the document updates itself according to event state, then it shouldn't need this extra onpopstate after onload because nothing needs to be changed. Ok, if I don't want it I can discard the first onpopstate. What if onpopstate after document parsing doesn't fire because the page was aborted during load? The links still work because DOMready was called. Of course I can use a variable to track current event state. But that's unnecessary. And what if i wanted to user to still see a 'page refresh' if he clicked on index.html twice, and clicked back? So how can I distinguish the initial onpopstate and other onpopstate? Do you see where the flaw is? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 14 December 2010 06:16:38 UTC