10437 2010-08-25 21:32:53 +0000 The pushState algorithm doesn't save the scroll position of the original history entry, but it should. See Mozilla bug 590573. 2010-10-04 14:29:39 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-history-pushstate P3 normal --- 1 contributor ian ian justin.lebar mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37858 0 contributor 2010-08-25 21:32:53 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-history-pushstate Comment: The pushState algorithm doesn't save the scroll position of the original history entry, but it should. See Mozilla bug 590573. Posted from: 63.245.220.240 39347 1 ian 2010-09-25 15:30:21 +0000 https://bugzilla.mozilla.org/show_bug.cgi?id=590573 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 39348 2 contributor 2010-09-25 15:32:15 +0000 Checked in as WHATWG revision r5485. Check-in comment: Also make pushState() store UA state such as scroll position. http://html5.org/tools/web-apps-tracker?from=5484&to=5485