Bug 19113 - History API: Clearly define popstate event behaviour on page load
Summary: History API: Clearly define popstate event behaviour on page load
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2012-09-28 12:27 UTC by Silvia Pfeiffer
Modified: 2012-10-06 00:51 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Silvia Pfeiffer 2012-09-28 12:27:36 UTC
Currently the spec for the new history API (history.pushState and popstate
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

Relates to WHATWG bugs:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18605 and

This will apply the following WHATWG patch:

Comment 1 Silvia Pfeiffer 2012-10-06 00:51:47 UTC
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:
Rationale: accepted WHATWG change