W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10537] New: document.readyState for aborted parser

From: <bugzilla@jessica.w3.org>
Date: Thu, 02 Sep 2010 23:33:01 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10537-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10537

           Summary: document.readyState for aborted parser
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: tonyg@chromium.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org, w3c@adambarth.com


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.

-- 
Configure bugmail: http://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 Thursday, 2 September 2010 23:33:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC