[html5] r6785 - [e] (0) strings should be marked with <code> for consistency Fixing http://www.w [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sun Oct 30 09:12:54 PDT 2011
Author: ianh
Date: 2011-10-30 09:12:52 -0700 (Sun, 30 Oct 2011)
New Revision: 6785
Modified:
complete.html
index
source
Log:
[e] (0) strings should be marked with <code> for consistency
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=14597
Modified: complete.html
===================================================================
--- complete.html 2011-10-29 16:06:05 UTC (rev 6784)
+++ complete.html 2011-10-30 16:12:52 UTC (rev 6785)
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 29 October 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 30 October 2011</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -9528,7 +9528,7 @@
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-readyState><a href=#dom-document-readystate>readyState</a></code></dt>
<dd>
- <p>Returns "loading" while the <code><a href=#document>Document</a></code> is loading, "interactive" once it is finished parsing but still loading sub-resources, and "complete" once it has loaded.</p>
+ <p>Returns "<code title="">loading</code>" while the <code><a href=#document>Document</a></code> is loading, "<code title="">interactive</code>" once it is finished parsing but still loading sub-resources, and "<code title="">complete</code>" once it has loaded.</p>
<p>The <code title=event-readystatechange><a href=#event-readystatechange>readystatechange</a></code> event fires on the <code><a href=#document>Document</a></code> object when this value changes.</p>
</dd>
@@ -9536,9 +9536,9 @@
<p>Each document has a <dfn id=current-document-readiness>current document readiness</dfn>. When a
<code><a href=#document>Document</a></code> object is created, it must have its
- <a href=#current-document-readiness>current document readiness</a> set to the string "loading"
+ <a href=#current-document-readiness>current document readiness</a> set to the string "<code title="">loading</code>"
if the document is associated with an <a href=#html-parser>HTML parser</a> or an
- <a href=#xml-parser>XML parser</a>, or to the string "complete" otherwise.
+ <a href=#xml-parser>XML parser</a>, 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 <a href=#fire-a-simple-event>fire a simple event</a>
named <dfn id=event-readystatechange title=event-readystatechange><code>readystatechange</code></dfn>
@@ -10012,7 +10012,7 @@
without firing any mutation events.</li> <!-- as of 2010-07-26,
only Opera fired mutation events here. -->
- <li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "loading".</li>
+ <li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "<code title="">loading</code>".</li>
<li><p><!--SYNCLOAD If <code title="dom-XMLDocument-async">async</code> is
set to true, then run--> Run the remainder of these steps asynchronously,
@@ -10052,7 +10052,7 @@
set to true, then <span>queue--> <a href=#queue-a-task>Queue a task</a> to run the following
steps. <!--SYNCLOAD Otherwise, run them synchronously.--></p>
- <ol><li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "complete".</li>
+ <ol><li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "<code title="">complete</code>".</li>
<li><p>Replace all the children of <var title="">document</var>
by the children of <var title="">result</var> (even if it has no
@@ -13012,7 +13012,7 @@
<i>irrelevant</i>.</li>
<li><p>Set the <a href=#current-document-readiness>current document readiness</a> of the
- document to "loading".</li>
+ document to "<code title="">loading</code>".</li>
<li>
@@ -65039,7 +65039,7 @@
of those elements.</li>
<li><p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is
- "complete", <a href=#queue-a-task>queue a task</a> to fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event at the
+ "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event at the
<code><a href=#window>Window</a></code> object of that <code><a href=#document>Document</a></code>, but
with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
<code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
@@ -90804,7 +90804,7 @@
the document, the user agent must run the following steps:</p>
<ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href=#current-document-readiness>current document readiness</a> to
- "interactive" <!-- this also synchronously fires an event --> and
+ "<code title="">interactive</code>" <!-- this also synchronously fires an event --> and
the <a href=#insertion-point>insertion point</a> to undefined.</li>
<li><p>Pop <em>all</em> the nodes off the <a href=#stack-of-open-elements>stack of open
@@ -90855,7 +90855,7 @@
the <code><a href=#document>Document</a></code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to set the <a href=#current-document-readiness>current document
- readiness</a> to "complete". <!-- this also fires an event
+ readiness</a> to "<code title="">complete</code>". <!-- this also fires an event
synchronously during the task --></li>
<li><p>If the <code><a href=#document>Document</a></code> is in a <a href=#browsing-context>browsing
Modified: index
===================================================================
--- index 2011-10-29 16:06:05 UTC (rev 6784)
+++ index 2011-10-30 16:12:52 UTC (rev 6785)
@@ -240,7 +240,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 29 October 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 30 October 2011</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -9528,7 +9528,7 @@
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-readyState><a href=#dom-document-readystate>readyState</a></code></dt>
<dd>
- <p>Returns "loading" while the <code><a href=#document>Document</a></code> is loading, "interactive" once it is finished parsing but still loading sub-resources, and "complete" once it has loaded.</p>
+ <p>Returns "<code title="">loading</code>" while the <code><a href=#document>Document</a></code> is loading, "<code title="">interactive</code>" once it is finished parsing but still loading sub-resources, and "<code title="">complete</code>" once it has loaded.</p>
<p>The <code title=event-readystatechange><a href=#event-readystatechange>readystatechange</a></code> event fires on the <code><a href=#document>Document</a></code> object when this value changes.</p>
</dd>
@@ -9536,9 +9536,9 @@
<p>Each document has a <dfn id=current-document-readiness>current document readiness</dfn>. When a
<code><a href=#document>Document</a></code> object is created, it must have its
- <a href=#current-document-readiness>current document readiness</a> set to the string "loading"
+ <a href=#current-document-readiness>current document readiness</a> set to the string "<code title="">loading</code>"
if the document is associated with an <a href=#html-parser>HTML parser</a> or an
- <a href=#xml-parser>XML parser</a>, or to the string "complete" otherwise.
+ <a href=#xml-parser>XML parser</a>, 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 <a href=#fire-a-simple-event>fire a simple event</a>
named <dfn id=event-readystatechange title=event-readystatechange><code>readystatechange</code></dfn>
@@ -10012,7 +10012,7 @@
without firing any mutation events.</li> <!-- as of 2010-07-26,
only Opera fired mutation events here. -->
- <li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "loading".</li>
+ <li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "<code title="">loading</code>".</li>
<li><p><!--SYNCLOAD If <code title="dom-XMLDocument-async">async</code> is
set to true, then run--> Run the remainder of these steps asynchronously,
@@ -10052,7 +10052,7 @@
set to true, then <span>queue--> <a href=#queue-a-task>Queue a task</a> to run the following
steps. <!--SYNCLOAD Otherwise, run them synchronously.--></p>
- <ol><li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "complete".</li>
+ <ol><li><p>Set the <a href=#current-document-readiness>current document readiness</a> of <var title="">document</var> to "<code title="">complete</code>".</li>
<li><p>Replace all the children of <var title="">document</var>
by the children of <var title="">result</var> (even if it has no
@@ -13012,7 +13012,7 @@
<i>irrelevant</i>.</li>
<li><p>Set the <a href=#current-document-readiness>current document readiness</a> of the
- document to "loading".</li>
+ document to "<code title="">loading</code>".</li>
<li>
@@ -65039,7 +65039,7 @@
of those elements.</li>
<li><p>If the <a href=#current-document-readiness>current document readiness</a> of the <var title="">specified entry</var>'s <code><a href=#document>Document</a></code> is
- "complete", <a href=#queue-a-task>queue a task</a> to fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event at the
+ "<code title="">complete</code>", <a href=#queue-a-task>queue a task</a> to fire a <code title=event-pageshow><a href=#event-pageshow>pageshow</a></code> event at the
<code><a href=#window>Window</a></code> object of that <code><a href=#document>Document</a></code>, but
with its <code title=dom-event-target><a href=#dom-event-target>target</a></code> set to the
<code><a href=#document>Document</a></code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
@@ -90804,7 +90804,7 @@
the document, the user agent must run the following steps:</p>
<ol><!-- this happens as part of one of the tasks that runs the parser --><li><p>Set the <a href=#current-document-readiness>current document readiness</a> to
- "interactive" <!-- this also synchronously fires an event --> and
+ "<code title="">interactive</code>" <!-- this also synchronously fires an event --> and
the <a href=#insertion-point>insertion point</a> to undefined.</li>
<li><p>Pop <em>all</em> the nodes off the <a href=#stack-of-open-elements>stack of open
@@ -90855,7 +90855,7 @@
the <code><a href=#document>Document</a></code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to set the <a href=#current-document-readiness>current document
- readiness</a> to "complete". <!-- this also fires an event
+ readiness</a> to "<code title="">complete</code>". <!-- this also fires an event
synchronously during the task --></li>
<li><p>If the <code><a href=#document>Document</a></code> is in a <a href=#browsing-context>browsing
Modified: source
===================================================================
--- source 2011-10-29 16:06:05 UTC (rev 6784)
+++ source 2011-10-30 16:12:52 UTC (rev 6785)
@@ -9601,7 +9601,7 @@
<dt><var title="">document</var> . <code title="dom-document-readyState">readyState</code></dt>
<dd>
- <p>Returns "loading" while the <code>Document</code> is loading, "interactive" once it is finished parsing but still loading sub-resources, and "complete" once it has loaded.</p>
+ <p>Returns "<code title="">loading</code>" while the <code>Document</code> is loading, "<code title="">interactive</code>" once it is finished parsing but still loading sub-resources, and "<code title="">complete</code>" once it has loaded.</p>
<p>The <code title="event-readystatechange">readystatechange</code> event fires on the <code>Document</code> object when this value changes.</p>
</dd>
@@ -9611,9 +9611,9 @@
<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"
+ <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 "complete" otherwise.
+ <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
@@ -10199,7 +10199,7 @@
only Opera fired mutation events here. -->
<li><p>Set the <span>current document readiness</span> of <var
- title="">document</var> to "loading".</p></li>
+ title="">document</var> to "<code title="">loading</code>".</p></li>
<li><p><!--SYNCLOAD If <code title="dom-XMLDocument-async">async</code> is
set to true, then run--> Run the remainder of these steps asynchronously,
@@ -10249,7 +10249,7 @@
<ol>
<li><p>Set the <span>current document readiness</span> of <var
- title="">document</var> to "complete".</p></li>
+ title="">document</var> to "<code title="">complete</code>".</p></li>
<li><p>Replace all the children of <var title="">document</var>
by the children of <var title="">result</var> (even if it has no
@@ -13595,7 +13595,7 @@
<i>irrelevant</i>.</p></li>
<li><p>Set the <span>current document readiness</span> of the
- document to "loading".</p></li>
+ document to "<code title="">loading</code>".</p></li>
<li>
@@ -73780,7 +73780,7 @@
<li><p>If the <span>current document readiness</span> of the <var
title="">specified entry</var>'s <code>Document</code> is
- "complete", <span>queue a task</span> to fire a <code
+ "<code title="">complete</code>", <span>queue a task</span> to fire a <code
title="event-pageshow">pageshow</code> event at the
<code>Window</code> object of that <code>Document</code>, but
with its <code title="dom-event-target">target</code> set to the
@@ -102814,7 +102814,7 @@
<!-- this happens as part of one of the tasks that runs the parser -->
<li><p>Set the <span>current document readiness</span> to
- "interactive" <!-- this also synchronously fires an event --> and
+ "<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
@@ -102870,7 +102870,7 @@
the <code>Document</code>.</p></li>
<li><p><span>Queue a task</span> to set the <span>current document
- readiness</span> to "complete". <!-- this also fires an event
+ readiness</span> to "<code title="">complete</code>". <!-- this also fires an event
synchronously during the task --></p></li>
<li><p>If the <code>Document</code> is in a <span>browsing
More information about the Commit-Watchers
mailing list