18178 2012-07-18 17:33:43 +0000 The navigating to a fragment identifier" algorithm shouldn't be async 2013-04-29 22:38:27 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Linux RESOLVED FIXED exclusion P2 normal --- 1 contributor dave.null ian james mike public-html-admin public-html-wg-issue-tracking travil public-html-bugzilla oldest_to_newest 70822 0 contributor 2012-07-18 17:33:43 +0000 This was was cloned from bug 17155 as part of operation convergence. Originally filed: 2012-05-23 09:53:00 +0000 Original reporter: James Graham <jgraham@opera.com> ================================================================================ #0 James Graham 2012-05-23 09:53:34 +0000 -------------------------------------------------------------------------------- When UAs navigate to fragment identifiers they seem to do it in a sync way i.e. location.hash = "#bar" //location.hash is now "#bar" However the hashchange event seems to be queued rather than fired synchronously so that location.hash = "foo" onhashchange = function(e) {document.body.innerHTML += "<p> " + e.oldURL + " " + e.newURL} location.hash = "bar" causes the event to be fired twice. For other navigations, the async behaviour seems to be correct. ================================================================================ #1 James Graham 2012-05-23 10:01:30 +0000 -------------------------------------------------------------------------------- Also, the scrolling seems to happen synchronously ================================================================================ 86961 1 travil 2013-04-29 22:38:27 +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: Accepted Change Description: Fix ported from WHATWG spec