12521 2011-04-18 17:14:16 +0000 The document.readyState authoring usage note doesn't match the implementation requirements 2011-08-04 05:16:41 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#current-document-readiness P3 normal --- 1 contributor ian ayg lachlan.hunt mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 47537 0 contributor 2011-04-18 17:14:16 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Section: http://www.whatwg.org/specs/web-apps/current-work/#current-document-readiness Comment: The document.readyState authoring usage note doesn't match the implementation requirements Posted from: 213.236.208.247 by lachlan.hunt@lachy.id.au User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0a1) Gecko/20110417 Firefox/6.0a1 47538 1 lachlan.hunt 2011-04-18 17:16:32 +0000 The authoring usage note says it might return "interactive". The implementation requirements that follow do not define that value. 50270 2 ayg 2011-06-24 18:50:27 +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: Rejected Change Description: no spec change Rationale: The implementation requirements right afterward say "Various algorithms during page loading affect this value", and indeed the HTML parser sets readyState to "interactive" when it's done: http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-end So it looks like there's no spec bug here. 53719 3 mike 2011-08-04 05:16:41 +0000 mass-move component to LC1