This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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