8417 2009-12-02 09:27:18 +0000 "user agents must yield to whatever script invoked the navigation steps" should also allow tasks to continue, with the rest of the algorithm being async, so that the event loop doesn't block waiting for data. 2010-10-04 13:55:16 +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/#navigate P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 29882 0 contributor 2009-12-02 09:27:18 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#navigate Comment: "user agents must yield to whatever script invoked the navigation steps" should also allow tasks to continue, with the rest of the algorithm being async, so that the event loop doesn't block waiting for data. Posted from: 98.248.33.53 30557 1 ian 2010-01-06 03:32:46 +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: see diff given below Rationale: Concurred with reporter's comments. 30559 2 contributor 2010-01-06 03:33:44 +0000 Checked in as WHATWG revision r4495. Check-in comment: Navigation should be async. This wasn't properly described before. http://html5.org/tools/web-apps-tracker?from=4494&to=4495