10537 2010-09-02 23:33:01 +0000 document.readyState for aborted parser 2010-10-04 14:45:40 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED WONTFIX P1 critical --- 1 tonyg ian ian mike public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 38436 0 tonyg 2010-09-02 23:33:01 +0000 I'm working to implement the HTML5 document.readyState behavior for WebKit: https://bugs.webkit.org/show_bug.cgi?id=45119 According to http://www.whatwg.org/specs/web-apps/current-work/#the-end, the current document readiness is only updated in the "stops parsing" steps, but not in the "abort an HTML parser" steps. To my reading, this means that if the load is aborted, the readyState will remain "loading" or "interactive" forever. The legacy WebKit behavior is to switch to "complete" upon aborting. The legacy behavior actually seems more sane to me. I just wanted to confirm whether this is intentional, a spec bug, or perhaps I'm just misunderstanding the spec. 39409 1 ian 2010-09-25 20:44:54 +0000 The "abort an HTML parser" algorithm is only invoked in the case of calling document.open(), and that algorithm immediately sets the readiness to 'loading'. What happens in the case of a user-initiated abort is not defined in the HTML spec (interop in that case doesn't matter — by definition the user can't expect the page to work anyway). 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: Rejected Change Description: no spec change Rationale: see above