[Bug 17155] New: The navigating to a fragment identifier" algorithm shouldn't be async

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17155

           Summary: The navigating to a fragment identifier" algorithm
                    shouldn't be async
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jgraham@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org


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.

-- 
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 Wednesday, 23 May 2012 09:53:37 UTC