Short URL: http://html5.org/r/7169
Index: source
===================================================================
--- source (revision 7168)
+++ source (revision 7169)
@@ -10287,7 +10287,7 @@
<code>Document</code> was created.</p>
<p>A <code>Document</code> object that falls into one of the
- following conditions is a <dfn>cookie-free <code>Document</code>
+ following conditions is a <dfn>cookie-averse <code>Document</code>
object</dfn>:</p>
<ul>
@@ -10302,12 +10302,12 @@
</ul>
<!--Other specifications can also define <code>Document</code>
- objects as being <span title="cookie-free Document
- object">cookie-free <code>Document</code> objects</span>.-->
+ objects as being <span title="cookie-averse Document
+ object">cookie-averse <code>Document</code> objects</span>.-->
<p id="sandboxCookies">On getting, if the document is a
- <span>cookie-free <code>Document</code> object</span>, then the user
- agent must return the empty string. Otherwise, if the
+ <span>cookie-averse <code>Document</code> object</span>, then the
+ user agent must return the empty string. Otherwise, if the
<code>Document</code>'s <span>origin</span> is not a
scheme/host/port tuple, the user agent must throw a
<code>SecurityError</code> exception. Otherwise, the user agent must
@@ -10316,7 +10316,7 @@
"non-HTTP" API, <span>decoded as UTF-8, with error handling</span>.
<a href="#refsCOOKIES">[COOKIES]</a></p>
- <p>On setting, if the document is a <span>cookie-free
+ <p>On setting, if the document is a <span>cookie-averse
<code>Document</code> object</span>, then the user agent must do
nothing. Otherwise, if the <code>Document</code>'s
<span>origin</span> is not a scheme/host/port tuple, the user agent
@@ -10326,7 +10326,8 @@
set-cookie-string">receiving a set-cookie-string</span> for
<span>the document's address</span> via a "non-HTTP" API, consisting
of the new value encoded as UTF-8. <a
- href="#refsCOOKIES">[COOKIES]</a> <a href="#refsRFC3629">[RFC3629]</a></p>
+ href="#refsCOOKIES">[COOKIES]</a> <a
+ href="#refsRFC3629">[RFC3629]</a></p>
<p class="note">Since the <code
title="dom-document-cookie">cookie</code> attribute is accessible
@@ -10420,12 +10421,13 @@
<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 "<code title="">loading</code>"
- if the document is associated with an <span>HTML parser</span> or an
- <span>XML parser</span>, or to the string "<code title="">complete</code>" otherwise.
- Various algorithms during page loading affect this value. When the
- value is set, the user agent must <span>fire a simple event</span>
- named <dfn
+ <span>current document readiness</span> set to the string "<code
+ title="">loading</code>" if the document is associated with an
+ <span>HTML parser</span>, an <span>XML parser</span>, or an XSLT
+ processor, and to the string "<code title="">complete</code>"
+ otherwise. Various algorithms during page loading affect this value.
+ When the value is set, the user agent must <span>fire a simple
+ event</span> named <dfn
title="event-readystatechange"><code>readystatechange</code></dfn>
at the <code>Document</code> object.</p>
@@ -14406,10 +14408,31 @@
unaffected.) <a href="#refsXSLT10">[XSLT10]</a></p> <!-- note:
version matters for this ref -->
- <p class="note">There are also additional comments regarding the
- interaction of XSLT and HTML <a href="#scriptTagXSLT">in the
- <code>script</code> element section</a>.</p>
+ <hr>
+ <p>This specification does not specify precisely how XSLT processing
+ interacts with the <span>HTML parser</span> infrastructure (for
+ example, whether an XSLT processor acts as if it puts any elements
+ into a <span>stack of open elements</span>). However, XSLT
+ processors must <span>stop parsing</span> if they successfully
+ complete, and must set the <span>current document readiness</span>
+ first to "<code title="">interactive</code>"<!-- this synchronously
+ fires an event --> and then to "<code title="">complete</code>"<!--
+ this also synchronously fires an event --> if they are aborted.</p>
+
+ <hr>
+
+ <p>This specification does not specify how XSLT interacts with the
+ <span title="navigate">navigation</span> algorithm, how it fits in
+ with the <span>event loop</span>, nor how error pages are to be
+ handled (e.g. whether XSLT errors are to replace an incremental XSLT
+ output, or are rendered inline, etc).</p>
+
+ <p class="note">There are also additional non-normative comments
+ regarding the interaction of XSLT and HTML <a
+ href="#scriptTagXSLT">in the <code>script</code> element
+ section</a>.</p>
+
</div>
@@ -18531,12 +18554,9 @@
<!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
<p>This specification does not define how XSLT interacts with the
- <code>script</code> element (or, indeed, how XSLT processing
- triggers the <span>stop parsing</span> steps, how it interacts with
- the <span title="navigate">navigation</span> algorithm, or how it
- fits in with the <span>event loop</span>). However, in the absence
- of another specification actually defining this, here are some
- guidelines for implementors, based on existing implementations:</p>
+ <code>script</code> element. However, in the absence of another
+ specification actually defining this, here are some guidelines for
+ implementors, based on existing implementations:</p>
<ul>
@@ -77338,9 +77358,10 @@
attempt to <span>navigate</span> the <span>browsing context</span>
and that attempt is not currently running the <span>unload a
document</span> algorithm, cancel that <span
- title="navigate">navigation</span> and any associated instances of
- the <span title="fetch">fetch algorithm</span>. Otherwise, it must
- do nothing.</p>
+ title="navigate">navigation</span>; then, it must <span title="abort
+ a document">abort</span> the <span>active document</span> of the
+ <span>browsing context</span> of the <code>Window</code> object on
+ which it was invoked.</p>
</div>
@@ -108002,9 +108023,10 @@
<!-- this happens as part of one of the tasks that runs the parser -->
- <li><p>Set the <span>current document readiness</span> to
- "<code title="">interactive</code>" <!-- this also synchronously fires an event --> and
- the <span>insertion point</span> to undefined.</p></li>
+ <li><p>Set the <span>current document readiness</span> to "<code
+ title="">interactive</code>" <!-- this also synchronously fires an
+ event --> and the <span>insertion point</span> to
+ undefined.</p></li>
<li><p>Pop <em>all</em> the nodes off the <span>stack of open
elements</span>.</p></li>
@@ -108117,6 +108139,14 @@
<li><p>Pop <em>all</em> the nodes off the <span>stack of open
elements</span>.</p></li>
+ <li><p>Set the <span>current document readiness</span> to "<code
+ title="">interactive</code>"<!-- this synchronously fires an event
+ -->.</p></li>
+
+ <li><p>Set the <span>current document readiness</span> to "<code
+ title="">complete</code>"<!-- this also synchronously fires an
+ event -->.</p></li>
+
<!-- anything else? this is things that happen when you call
document.open() on a document that's still being parsed, or when
you navigate a document that's still parsing, or navigate the