10365 2010-08-14 12:19:57 +0000 popstate event fires after onload (first page visit) -- intended behavior? would be annoying if there was a script that ajax loaded a page at onpopstate, and hand typing in a url, the page is returned by the server, and then onpopstate fires after onload, 2010-11-13 20:31:35 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#event-popstate P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37413 0 contributor 2010-08-14 12:19:57 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#event-popstate Comment: popstate event fires after onload (first page visit) -- intended behavior? would be annoying if there was a script that ajax loaded a page at onpopstate, and hand typing in a url, the page is returned by the server, and then onpopstate fires after onload, and the browser/javascript requests the same page again with ajax. I think popstate should not fire after onload. if a script needs it then they should attach to both onpopstate and onload instead. Posted from: 219.77.175.157 39231 1 ian 2010-09-24 00:44:28 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It only fires after onload if you've gone back or forward in the history. Am I misunderstanding something here? The problem described doesn't seem to exist. 41877 2 henry.fai.hang.chan 2010-10-31 01:52:20 +0000 Firefox and chrome fires onpopstate after onload even without going back/forward. Is this a spec error or implementation problem? Should the spec clarify if a page load (just entering into location bar, no back/forward) counts as "navigating to a session history entry"? 41878 3 930 henry.fai.hang.chan 2010-10-31 01:52:58 +0000 Created attachment 930 test for firing of popstate and onload 42007 4 ian 2010-11-03 07:47:11 +0000 The spec seems completely unambiguous here — search for the string "fire a popstate event" for the only two occurrences, neither of which can happen without history traversal. Regarding the question in comment 2, a page load results in the "navigate" algorithm being invoked, which unambiguously results in history traversal. Thus what you describe is an implementation bug. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Not a spec bug. 42507 5 ian 2010-11-13 20:31:35 +0000 The comment in http://code.google.com/p/chromium/issues/detail?id=63040 is right, I made a mistake: popstate will fire after load with a 'null' state object, even without going back/forward. I missed that the state object is set to null if history traversal occurs without state (we changed that at some point). This is as designed, though; the popstate event handler is expected to grab the appropriate data given the provided state object. It's easy to not grab data if the state is null. 930 2010-10-31 01:52:58 +0000 2010-10-31 01:52:58 +0000 test for firing of popstate and onload test-popstate.html text/html 119 henry.fai.hang.chan PHNjcmlwdD4NCndpbmRvdy5vbnBvcHN0YXRlID0gZnVuY3Rpb24oKXthbGVydCgnb25wb3BzdGF0 ZScpfTsNCndpbmRvdy5vbmxvYWQgPSBmdW5jdGlvbigpe2FsZXJ0KCdvbmxvYWQnKX07DQo8L3Nj cmlwdD4=