19113 2012-09-28 12:27:36 +0000 History API: Clearly define popstate event behaviour on page load 2012-10-06 00:51:47 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED FIXED P2 normal --- 1 silviapfeiffer1 silviapfeiffer1 mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 74789 0 silviapfeiffer1 2012-09-28 12:27:36 +0000 Currently the spec for the new history API (history.pushState and popstate event, http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html) is ambigous about when to trigger a popstate event, at least ambigous enough for Chrome/Safari and Firefox to differ in a severe way (from an API user perspective). Relates to WHATWG bugs: https://www.w3.org/Bugs/Public/show_bug.cgi?id=18605 and https://www.w3.org/Bugs/Public/show_bug.cgi?id=18405 This will apply the following WHATWG patch: https://github.com/w3c/html/commit/a6b27250d8a00220eda5a906441af1594383677e 75457 1 silviapfeiffer1 2012-10-06 00:51:47 +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-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/a6b27250d8a00220eda5a906441af1594383677e Rationale: accepted WHATWG change