Skip to content
Permalink
Browse files

[] (0) First attempt at making document.readyState start off as 'comp…

…lete' for anything but a parser-associated document.

git-svn-id: http://svn.whatwg.org/webapps@2599 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Dec 28, 2008
1 parent dca7d91 commit fadfcb663e42ad4bea58e33d00333c82c4dd40f1
Showing with 28 additions and 10 deletions.
  1. +14 −5 index
  2. +14 −5 source
19 index
@@ -1379,8 +1379,8 @@
<p>The term <a href=#html-documents>HTML documents</a> is sometimes used in
contrast with <a href=#xml-documents>XML documents</a> to specifically mean
documents that were parsed using an <a href=#html-parser>HTML parser</a> (as
opposed to using an XML parser or created purely through the
DOM).</p>
opposed to using an <span>XML parser</span> or created purely
through the DOM).</p>

<p>Generally, when the specification states that a feature applies
to HTML or XHTML, it also includes the other. When a feature
@@ -6053,13 +6053,22 @@ interface <dfn id=domstringmap-0>DOMStringMap</dfn> {};</pre>

<p>Each document has a <dfn id=current-document-readiness>current document readiness</dfn>. When a
<code>Document</code> object is created, it must have its
<a href=#current-document-readiness>current document readiness</a> set to the string
"loading". Various algorithms during page loading affect this
<a href=#current-document-readiness>current document readiness</a> set to the string "loading"
if the document is associated with an <a href=#html-parser>HTML parser</a> or an
<span>XML parser</span>, or to the string "complete"
otherwise. Various algorithms during page loading affect this
value. When the value is set, the user agent must <a href=#fire-a-simple-event>fire a
simple event</a> called <code title=event-readystatechanged>readystatechanged</code> at the
simple event</a> called <code title=event-readystatechange>readystatechange</code> at the
<code>Document</code> object.</p> <!-- XXX define
document.onreadystatechange -->

<p>When a <code>Document</code> is created by an <span>XML
parser</span>, the <a href=#current-document-readiness>current document readiness</a> must be
changed to "complete" when the parser reaches the end of its input
stream.</p> <!-- XXX this should be in its own section, and we
should define 'delay the load event' for XML parsing so that we can
have the "interactive" state here too. -->

<p>The <dfn id=dom-document-readystate title=dom-document-readyState><code>readyState</code></dfn> DOM
attribute must, on getting, return the <a href=#current-document-readiness>current document
readiness</a>.</p>
19 source
@@ -402,8 +402,8 @@
<p>The term <span>HTML documents</span> is sometimes used in
contrast with <span>XML documents</span> to specifically mean
documents that were parsed using an <span>HTML parser</span> (as
opposed to using an XML parser or created purely through the
DOM).</p>
opposed to using an <span>XML parser</span> or created purely
through the DOM).</p>

<p>Generally, when the specification states that a feature applies
to HTML or XHTML, it also includes the other. When a feature
@@ -6080,14 +6080,23 @@ interface <dfn>DOMStringMap</dfn> {};</pre>

<p>Each document has a <dfn>current document readiness</dfn>. When a
<code>Document</code> object is created, it must have its
<span>current document readiness</span> set to the string
"loading". Various algorithms during page loading affect this
<span>current document readiness</span> set to the string "loading"
if the document is associated with an <span>HTML parser</span> or an
<span>XML parser</span>, or to the string "complete"
otherwise. Various algorithms during page loading affect this
value. When the value is set, the user agent must <span>fire a
simple event</span> called <code
title="event-readystatechanged">readystatechanged</code> at the
title="event-readystatechange">readystatechange</code> at the
<code>Document</code> object.</p> <!-- XXX define
document.onreadystatechange -->

<p>When a <code>Document</code> is created by an <span>XML
parser</span>, the <span>current document readiness</span> must be
changed to "complete" when the parser reaches the end of its input
stream.</p> <!-- XXX this should be in its own section, and we
should define 'delay the load event' for XML parsing so that we can
have the "interactive" state here too. -->

<p>The <dfn
title="dom-document-readyState"><code>readyState</code></dfn> DOM
attribute must, on getting, return the <span>current document

0 comments on commit fadfcb6

Please sign in to comment.
You can’t perform that action at this time.