- From: <bugzilla@jessica.w3.org>
- Date: Fri, 28 Sep 2012 12:27:36 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19113 Summary: History API: Clearly define popstate event behaviour on page load Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec AssignedTo: silviapfeiffer1@gmail.com ReportedBy: silviapfeiffer1@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org 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 -- Configure bugmail: https://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 Friday, 28 September 2012 12:27:37 UTC