[html5] r6005 - [e] (0) make it easier to track in which ways the specs are forking, to make it [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Apr 13 17:39:57 PDT 2011
Author: ianh
Date: 2011-04-13 17:39:55 -0700 (Wed, 13 Apr 2011)
New Revision: 6005
Modified:
complete.html
index
source
Log:
[e] (0) make it easier to track in which ways the specs are forking, to make it easier to reduce it later.
Modified: complete.html
===================================================================
--- complete.html 2011-04-13 23:50:15 UTC (rev 6004)
+++ complete.html 2011-04-14 00:39:55 UTC (rev 6005)
@@ -239,7 +239,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 13 April 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 14 April 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -3648,7 +3648,7 @@
requirements in this specification. When someone applying this
specification to their activities decides that they will recognize
the requirements of such an extension specification, it becomes an
-<!--CONFORMANCE-->
+<!--CONFORMANCE--><!--FORK-->
<dfn id=other-applicable-specifications title="other applicable specifications">applicable
specification</dfn> for the purposes of conformance requirements in
this specification.</p>
@@ -12139,9 +12139,9 @@
new instances of those objects. (This includes in particular the
<code><a href=#window>Window</a></code>, <code><a href=#location>Location</a></code>, <code><a href=#history-0>History</a></code>,
<code><a href=#applicationcache>ApplicationCache</a></code>,
-
+<!--UNDO-->
<code><a href=#undomanager>UndoManager</a></code>,
-
+<!--UNDO-->
and <code><a href=#navigator>Navigator</a></code>, objects, the various
<code><a href=#barprop>BarProp</a></code> objects, the two <code><a href=#storage-0>Storage</a></code> objects,
the various <code><a href=#htmlcollection>HTMLCollection</a></code> objects, and objects
@@ -21828,13 +21828,13 @@
display any image, or to prevent any image from being
displayed.
- <!--POLITICS-->
+ <!--POLITICS--><!--FORK-->
User agents may also apply heuristics to help the user make use of
the image when the user is unable to see it, e.g. due to a visual
disability or because they are using a text terminal with no
graphics capabilities. Such heuristics could include, for instance,
optical character recognition (OCR) of text found within the image.
- <!--POLITICS-->
+ <!--POLITICS--><!--FORK-->
</p>
@@ -22471,12 +22471,13 @@
in the markup of the document.</p>
-
<!-- The above paragraph is omitted in the WHATWG copy and replaced
with the explicit requirement below because accessibility is better
served by having authors get all their information from one place,
instead of requiring them to read multiple (contradictory) documents. -->
+<!--FORK-->
+
<p>However, a decorative image that isn't discussed by the
surrounding text but still has some relevance can be included in a page
using the <code><a href=#the-img-element>img</a></code> element. Such images are decorative, but
@@ -22506,9 +22507,9 @@
</div>
+<!--FORK-->
-
<h6 id=a-group-of-images-that-form-a-single-larger-picture-with-no-links><span class=secno>4.8.1.1.8 </span>A group of images that form a single larger picture with no links</h6>
<p>When a picture has been sliced into smaller image files that are
@@ -26047,15 +26048,15 @@
resource</a>.</p>
<p class=note>
-
+ <!--FORK-->
Only the <a href=#mime-type>MIME type</a> <!-- the WG decision started with the next bit, which is not in the style of the spec -->
-
+ <!--FORK-->
"<code>application/octet-stream</code>"
-
+ <!--FORK-->
with no parameters
-
+ <!--FORK-->
is special-cased here; if any parameter appears with it, it
-
+ <!--FORK-->
will <!-- the WG decision that led to this text had a "should", but this is a non-normative section -->
be treated just like any other <a href=#mime-type>MIME type</a>.
@@ -30816,7 +30817,7 @@
</table></div>
<!--KEEP-START w3c-html--><!--TT-->
-<!--TT-->
+<!--TTVTT-->
<h5 id=webvtt-0><span class=secno>4.8.10.13 </span>WebVTT</h5>
@@ -32469,7 +32470,7 @@
<!--</div>-->
-<!--TT-->
+<!--TTVTT-->
<h5 id=user-interface><span class=secno>4.8.10.14 </span>User interface</h5>
@@ -37798,7 +37799,7 @@
the cell that corresponds to the values of the two dice.
</caption></pre>
- <!-- HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) -->
+<!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
<p>This provides the user with more context:</p>
<table class=dice-example><caption>
@@ -37815,7 +37816,7 @@
<tr><th> 4 <td> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10
<tr><th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
<tr><th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
- </table></div>
+ </table><!--HTML4POLICE--><!--FORK--></div>
@@ -39610,7 +39611,7 @@
<td>29.0%
</table></pre>
-<!--HTML4POLICE-->
+<!--HTML4POLICE--><!--FORK-->
<p>This table could look like this:</p>
<table class="apple-table-examples e1"><thead><tr><th>
@@ -39633,7 +39634,7 @@
<td>34.3%
<td>34.0%
<td>29.0%
- </table><!--HTML4POLICE--><hr><p>The following shows how one might mark up the operating expenses
+ </table><!--HTML4POLICE--><!--FORK--><hr><p>The following shows how one might mark up the operating expenses
table from lower on the same page of that document:</p>
<pre><table>
@@ -59408,9 +59409,9 @@
attribute DOMString <a href=#dom-name title=dom-name>name</a>; <!-- not [Replaceable] per WebKit and IE8 -->
[PutForwards=<a href=#dom-location-href title=dom-location-href>href</a>] readonly attribute <a href=#location>Location</a> <a href=#dom-location title=dom-location>location</a>;
readonly attribute <a href=#history-0>History</a> <a href=#dom-history title=dom-history>history</a>;
-
+<!--UNDO-->
readonly attribute <a href=#undomanager>UndoManager</a> <a href=#dom-undomanager title=dom-undoManager>undoManager</a>;
-
+<!--UNDO-->
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-locationbar title=dom-window-locationbar>locationbar</a>;
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-menubar title=dom-window-menubar>menubar</a>;
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-personalbar title=dom-window-personalbar>personalbar</a>;
@@ -71416,7 +71417,7 @@
</div>
-
+<!--UNDO-->
<h3 id=undo><span class=secno>8.8 </span><dfn>Undo history</dfn></h3>
<div class=impl>
@@ -71753,11 +71754,11 @@
no detectable difference.</p>
</div>
+<!--UNDO-->
-
<h3 id=editing-apis><span class=secno>8.9 </span>Editing APIs</h3>
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-execCommand><a href=#execCommand>execCommand</a></code>(<var title="">commandId</var> [, <var title="">showUI</var> [, <var title="">value</var> ] ] )</dt>
@@ -72099,9 +72100,9 @@
transaction history</a>, restoring the associated state. If the
<a href=#undo-position>undo position</a> is at the end of the <a href=#undo-transaction-history>undo
transaction history</a>, the user agent must do nothing.
-
+<!--UNDO-->
See the <a href=#undo>undo history</a>.
-
+<!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <a href=#undo-position>undo position</a>
is not at the end of the <a href=#undo-transaction-history>undo transaction
@@ -72162,9 +72163,9 @@
transaction history</a>, restoring the associated state. If the
<a href=#undo-position>undo position</a> is at the start of the <a href=#undo-transaction-history>undo
transaction history</a>, the user agent must do nothing.
-
+<!--UNDO-->
See the <a href=#undo>undo history</a>.
-
+<!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <a href=#undo-position>undo position</a>
is not at the start of the <a href=#undo-transaction-history>undo transaction
@@ -72217,7 +72218,7 @@
v2 (well, really v0):
"forecolor", "hilitecolor", "fontname", "fontsize", "justifyleft",
"justifycenter", "justifyright", "justifyfull", "indent", "outdent"
---><div data-component="other Hixie drafts (editor: Ian Hickson)">
+--><!--PEERCONNECTION--><div data-component="other Hixie drafts (editor: Ian Hickson)">
<h2 id=video-conferencing-and-peer-to-peer-communication><span class=secno>9 </span>Video conferencing and peer-to-peer communication</h2>
@@ -73943,6 +73944,7 @@
</div>
+<!--PEERCONNECTION-->
@@ -76119,6 +76121,7 @@
+<!--POSTMSG-->
<h2 id=comms><span class=secno>11 </span>Communication</h2>
@@ -76233,9 +76236,10 @@
</div><!--data-component-->
-
+<!--POSTMSG-->
+
<h3 id=server-sent-events><span class=secno>11.2 </span><dfn>Server-sent events</dfn></h3>
<div data-component="Server-Sent Events (editor: Ian Hickson)">
@@ -77440,8 +77444,8 @@
</div><!--data-component-->
-
+<!--POSTMSG-->
@@ -78144,9 +78148,12 @@
</div><!--data-component-->
+<!--POSTMSG-->
+
+
<div data-component="Web Storage (editor: Ian Hickson)">
<h2 id=webstorage><span class=secno>12 </span>Web storage</h2>
@@ -78836,7 +78843,6 @@
-
<h2 id=syntax><span class=secno>13 </span><dfn>The HTML syntax</dfn></h2>
<p class=note>This section only describes the rules for resources
@@ -93688,7 +93694,7 @@
<!--MD-->
-
+<!--PEERCONNECTION-->
<h3 id=application/html-peer-connection-data><span class=secno>17.8 </span><dfn><code>application/html-peer-connection-data</code></dfn></h3>
<p>This registration is for community review and will be submitted
@@ -93765,9 +93771,9 @@
<dd>W3C</dd>
</dl><p>Fragment identifiers used with <code><a href=#text/html>text/html</a></code> resources
refer to <a href=#the-indicated-part-of-the-document>the indicated part of the document</a>.</p>
+<!--PEERCONNECTION-->
-
<!--PING-->
<h3 id=ping-from><span class=secno>17.9 </span><dfn title=http-ping-from><code>Ping-From</code></dfn></h3>
@@ -97965,12 +97971,12 @@
features first widely deployed by the Windows Internet Explorer
browser.</p>
-
+<!--MD-->
<p>Thanks to the participants of the microdata usability study for
allowing us to use their mistakes as a guide for designing the
microdata feature.</p>
+<!--MD-->
-
<!--TT-->
<p>Thanks to the SubRip community, including in particular Zuggy and
ai4spam, for their work on the SubRip software program whose SRT
Modified: index
===================================================================
--- index 2011-04-13 23:50:15 UTC (rev 6004)
+++ index 2011-04-14 00:39:55 UTC (rev 6005)
@@ -243,7 +243,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><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 13 April 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 14 April 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -1335,11 +1335,12 @@
differ in a small number of ways. The main difference is that the
W3C version does not include some newer features, such as:</p>
- <ul class=brief><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--DEVICE-->
+ <ul class=brief><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONTROLLER-->
<li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
<li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TT--> <!--TTVTT-->
<li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
<li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
+ <li>An experimental <code><a href=#undomanager>UndoManager</a></code> interface.</li><!--UNDO-->
</ul><p>This is a result of the specifications having different
development modalities. The WHATWG specification is a continuously
maintained living standard, with maturity managed at a very granular
@@ -1354,18 +1355,18 @@
specification can as a whole reach a more mature state.</p>
<p>In addition to the above, there are some small differences,
- mostly editorial, between the two versions of the specification:</p>
+ mostly editorial, between the two versions of the specification:</p><!--FORK-->
<ul class=brief><li>Instead of this section, the W3C version has a different
paragraph explaining the difference between the W3C and WHATWG
versions of HTML.</li> <!-- in the status section -->
<li>The W3C version refers to the technology as HTML5, rather than
- just HTML.</li>
+ just HTML.</li><!--VERSION-->
<li>Examples that use features from HTML5 are not present in the
W3C version since the W3C version is published as HTML4 due to <a href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
- publication policies</a>.</li>
+ publication policies</a>.</li><!--HTML4POLICE-->
<li>The W3C version defines conformance for documents in a more
traditional (version-orientated) way, because of <a href=http://lists.w3.org/Archives/Public/public-html/2011Mar/0574.html>a
@@ -1394,11 +1395,11 @@
are currently published as separate specifications as well, and are
not included in the W3C HTML5 specification, consist of:</p>
- <ul class=brief><li><a href=#2dcontext>Canvas 2D Graphics Context</a>
- <li><a href=#microdata>Microdata</a>
+ <ul class=brief><li><a href=#2dcontext>Canvas 2D Graphics Context</a><!--2DCONTEXT-->
+ <li><a href=#microdata>Microdata</a><!--MD-->
<li><a href=#mdvocabs>Microdata vocabularies</a>
- <li><a href=#crossDocumentMessages>Cross-document messaging</a> (also known as Communications)
- <li><a href=#channel-messaging>Channel messaging</a> (also known as Communications)
+ <li><a href=#crossDocumentMessages>Cross-document messaging</a> (also known as Communications)<!--POSTMSG-->
+ <li><a href=#channel-messaging>Channel messaging</a> (also known as Communications)<!--POSTMSG-->
</ul><p>The <a href=#forms>forms</a> part of this specification was
previously published separately in a specification known as Web
Forms 2.</p>
@@ -3650,7 +3651,7 @@
requirements in this specification. When someone applying this
specification to their activities decides that they will recognize
the requirements of such an extension specification, it becomes an
-<!--CONFORMANCE-->
+<!--CONFORMANCE--><!--FORK-->
<dfn id=other-applicable-specifications title="other applicable specifications">applicable
specification</dfn> for the purposes of conformance requirements in
this specification.</p>
@@ -12141,9 +12142,9 @@
new instances of those objects. (This includes in particular the
<code><a href=#window>Window</a></code>, <code><a href=#location>Location</a></code>, <code><a href=#history-0>History</a></code>,
<code><a href=#applicationcache>ApplicationCache</a></code>,
-
+<!--UNDO-->
<code><a href=#undomanager>UndoManager</a></code>,
-
+<!--UNDO-->
and <code><a href=#navigator>Navigator</a></code>, objects, the various
<code><a href=#barprop>BarProp</a></code> objects, the two <code>Storage</code> objects,
the various <code><a href=#htmlcollection>HTMLCollection</a></code> objects, and objects
@@ -21830,13 +21831,13 @@
display any image, or to prevent any image from being
displayed.
- <!--POLITICS-->
+ <!--POLITICS--><!--FORK-->
User agents may also apply heuristics to help the user make use of
the image when the user is unable to see it, e.g. due to a visual
disability or because they are using a text terminal with no
graphics capabilities. Such heuristics could include, for instance,
optical character recognition (OCR) of text found within the image.
- <!--POLITICS-->
+ <!--POLITICS--><!--FORK-->
</p>
@@ -22473,12 +22474,13 @@
in the markup of the document.</p>
-
<!-- The above paragraph is omitted in the WHATWG copy and replaced
with the explicit requirement below because accessibility is better
served by having authors get all their information from one place,
instead of requiring them to read multiple (contradictory) documents. -->
+<!--FORK-->
+
<p>However, a decorative image that isn't discussed by the
surrounding text but still has some relevance can be included in a page
using the <code><a href=#the-img-element>img</a></code> element. Such images are decorative, but
@@ -22508,9 +22510,9 @@
</div>
+<!--FORK-->
-
<h6 id=a-group-of-images-that-form-a-single-larger-picture-with-no-links><span class=secno>4.8.1.1.8 </span>A group of images that form a single larger picture with no links</h6>
<p>When a picture has been sliced into smaller image files that are
@@ -26052,15 +26054,15 @@
resource</a>.</p>
<p class=note>
-
+ <!--FORK-->
Only the <a href=#mime-type>MIME type</a> <!-- the WG decision started with the next bit, which is not in the style of the spec -->
-
+ <!--FORK-->
"<code>application/octet-stream</code>"
-
+ <!--FORK-->
with no parameters
-
+ <!--FORK-->
is special-cased here; if any parameter appears with it, it
-
+ <!--FORK-->
will <!-- the WG decision that led to this text had a "should", but this is a non-normative section -->
be treated just like any other <a href=#mime-type>MIME type</a>.
@@ -30821,7 +30823,7 @@
</table></div>
<!--KEEP-START w3c-html--><!--TT-->
-<!--TT-->
+<!--TTVTT-->
<h5 id=webvtt-0><span class=secno>4.8.10.13 </span>WebVTT</h5>
@@ -32474,7 +32476,7 @@
<!--</div>-->
-<!--TT-->
+<!--TTVTT-->
<h5 id=user-interface><span class=secno>4.8.10.14 </span>User interface</h5>
@@ -37803,7 +37805,7 @@
the cell that corresponds to the values of the two dice.
</caption></pre>
- <!-- HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) -->
+<!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
<p>This provides the user with more context:</p>
<table class=dice-example><caption>
@@ -37820,7 +37822,7 @@
<tr><th> 4 <td> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10
<tr><th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
<tr><th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
- </table></div>
+ </table><!--HTML4POLICE--><!--FORK--></div>
@@ -39615,7 +39617,7 @@
<td>29.0%
</table></pre>
-<!--HTML4POLICE-->
+<!--HTML4POLICE--><!--FORK-->
<p>This table could look like this:</p>
<table class="apple-table-examples e1"><thead><tr><th>
@@ -39638,7 +39640,7 @@
<td>34.3%
<td>34.0%
<td>29.0%
- </table><!--HTML4POLICE--><hr><p>The following shows how one might mark up the operating expenses
+ </table><!--HTML4POLICE--><!--FORK--><hr><p>The following shows how one might mark up the operating expenses
table from lower on the same page of that document:</p>
<pre><table>
@@ -59413,9 +59415,9 @@
attribute DOMString <a href=#dom-name title=dom-name>name</a>; <!-- not [Replaceable] per WebKit and IE8 -->
[PutForwards=<a href=#dom-location-href title=dom-location-href>href</a>] readonly attribute <a href=#location>Location</a> <a href=#dom-location title=dom-location>location</a>;
readonly attribute <a href=#history-0>History</a> <a href=#dom-history title=dom-history>history</a>;
-
+<!--UNDO-->
readonly attribute <a href=#undomanager>UndoManager</a> <a href=#dom-undomanager title=dom-undoManager>undoManager</a>;
-
+<!--UNDO-->
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-locationbar title=dom-window-locationbar>locationbar</a>;
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-menubar title=dom-window-menubar>menubar</a>;
[Replaceable] readonly attribute <a href=#barprop>BarProp</a> <a href=#dom-window-personalbar title=dom-window-personalbar>personalbar</a>;
@@ -71447,7 +71449,7 @@
</div>
-
+<!--UNDO-->
<h3 id=undo><span class=secno>8.8 </span><dfn>Undo history</dfn></h3>
<div class=impl>
@@ -71784,11 +71786,11 @@
no detectable difference.</p>
</div>
+<!--UNDO-->
-
<h3 id=editing-apis><span class=secno>8.9 </span>Editing APIs</h3>
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-execCommand><a href=#execCommand>execCommand</a></code>(<var title="">commandId</var> [, <var title="">showUI</var> [, <var title="">value</var> ] ] )</dt>
@@ -72130,9 +72132,9 @@
transaction history</a>, restoring the associated state. If the
<a href=#undo-position>undo position</a> is at the end of the <a href=#undo-transaction-history>undo
transaction history</a>, the user agent must do nothing.
-
+<!--UNDO-->
See the <a href=#undo>undo history</a>.
-
+<!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <a href=#undo-position>undo position</a>
is not at the end of the <a href=#undo-transaction-history>undo transaction
@@ -72193,9 +72195,9 @@
transaction history</a>, restoring the associated state. If the
<a href=#undo-position>undo position</a> is at the start of the <a href=#undo-transaction-history>undo
transaction history</a>, the user agent must do nothing.
-
+<!--UNDO-->
See the <a href=#undo>undo history</a>.
-
+<!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <a href=#undo-position>undo position</a>
is not at the start of the <a href=#undo-transaction-history>undo transaction
@@ -72248,7 +72250,7 @@
v2 (well, really v0):
"forecolor", "hilitecolor", "fontname", "fontsize", "justifyleft",
"justifycenter", "justifyright", "justifyfull", "indent", "outdent"
---><div data-component="other Hixie drafts (editor: Ian Hickson)">
+--><!--PEERCONNECTION--><div data-component="other Hixie drafts (editor: Ian Hickson)">
<h2 id=video-conferencing-and-peer-to-peer-communication><span class=secno>9 </span>Video conferencing and peer-to-peer communication</h2>
@@ -73974,6 +73976,8 @@
</div>
+<!--PEERCONNECTION-->
+<!--POSTMSG-->
<h2 id=comms><span class=secno>10 </span>Communication</h2>
@@ -74092,10 +74096,11 @@
</div><!--data-component-->
+<!--POSTMSG-->
+<!--POSTMSG-->
-
<div data-component="Web Messaging (editor: Ian Hickson)">
@@ -74795,9 +74800,8 @@
</div><!--data-component-->
+<!--POSTMSG-->
-
-
<h2 id=syntax><span class=secno>11 </span><dfn>The HTML syntax</dfn></h2>
<p class=note>This section only describes the rules for resources
@@ -89649,7 +89653,7 @@
<!--MD-->
-
+<!--PEERCONNECTION-->
<h3 id=application/html-peer-connection-data><span class=secno>15.8 </span><dfn><code>application/html-peer-connection-data</code></dfn></h3>
<p>This registration is for community review and will be submitted
@@ -89726,9 +89730,9 @@
<dd>W3C</dd>
</dl><p>Fragment identifiers used with <code><a href=#text/html>text/html</a></code> resources
refer to <a href=#the-indicated-part-of-the-document>the indicated part of the document</a>.</p>
+<!--PEERCONNECTION-->
-
<!--PING-->
<h3 id=ping-from><span class=secno>15.9 </span><dfn title=http-ping-from><code>Ping-From</code></dfn></h3>
@@ -92776,12 +92780,12 @@
<td> <code><a href=#event>Event</a></code>
<td> Fired at the <code><a href=#document>Document</a></code> when it finishes parsing and again when all its subresources have finished loading
-
+<!--UNDO-->
<tr><td> <code title=event-redo><a href=#event-redo>redo</a></code>
<td> <code><a href=#undomanagerevent>UndoManagerEvent</a></code>
<td> Fired at the <code><a href=#window>Window</a></code> object when the user <a href=#redo:-moving-forward-in-the-undo-transaction-history title=do-redo>goes forward in the undo transaction history</a>
+<!--UNDO-->
-
<tr><td> <code title=event-reset>reset</code>
<td> <code><a href=#event>Event</a></code>
<td> Fired at a <code><a href=#the-form-element>form</a></code> element when it is <a href=#concept-form-reset title=concept-form-reset>reset</a>
@@ -92794,12 +92798,12 @@
<td> <code><a href=#event>Event</a></code>
<td> Fired at a <code><a href=#the-form-element>form</a></code> element when it is <a href=#concept-form-submit title=concept-form-submit>submitted</a>
-
+<!--UNDO-->
<tr><td> <code title=event-undo><a href=#event-undo>undo</a></code>
<td> <code><a href=#undomanagerevent>UndoManagerEvent</a></code>
<td> Fired at the <code><a href=#window>Window</a></code> object when the user <a href=#undo:-moving-back-in-the-undo-transaction-history title=do-undo>goes backward in the undo transaction history</a>
+<!--UNDO-->
-
<tr><td> <code title=event-unload>unload</code>
<td> <code><a href=#event>Event</a></code>
<td> Fired at the <code><a href=#window>Window</a></code> object when the page is going away
@@ -94086,12 +94090,12 @@
features first widely deployed by the Windows Internet Explorer
browser.</p>
-
+<!--MD-->
<p>Thanks to the participants of the microdata usability study for
allowing us to use their mistakes as a guide for designing the
microdata feature.</p>
+<!--MD-->
-
<!--TT-->
<p>Thanks to the SubRip community, including in particular Zuggy and
ai4spam, for their work on the SubRip software program whose SRT
Modified: source
===================================================================
--- source 2011-04-13 23:50:15 UTC (rev 6004)
+++ source 2011-04-14 00:39:55 UTC (rev 6005)
@@ -70,11 +70,12 @@
W3C version does not include some newer features, such as:</p>
<ul class="brief">
- <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--DEVICE-->
+ <li>The <code>PeerConnection</code> API and related video-conferencing features.</li> <!--PEERCONTROLLER-->
<li>The <code title="attr-hyperlink-ping">ping</code> attribute and related <span>hyperlink auditing</span> features.</li> <!--PING-->
<li>The <span>WebVTT</span> format and some <span>text track</span> API features.</li> <!--TT--> <!--TTVTT-->
<li>Rules for <a href="#atom">converting HTML to Atom</a>.</li> <!--MD-->
<li>The <code title="dom-document-cssElementMap">cssElementMap</code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
+ <li>An experimental <code>UndoManager</code> interface.</li><!--UNDO-->
</ul>
<p>This is a result of the specifications having different
@@ -91,7 +92,7 @@
specification can as a whole reach a more mature state.</p>
<p>In addition to the above, there are some small differences,
- mostly editorial, between the two versions of the specification:</p>
+ mostly editorial, between the two versions of the specification:</p><!--FORK-->
<ul class="brief">
@@ -100,12 +101,12 @@
versions of HTML.</li> <!-- in the status section -->
<li>The W3C version refers to the technology as HTML5, rather than
- just HTML.</li>
+ just HTML.</li><!--VERSION-->
<li>Examples that use features from HTML5 are not present in the
W3C version since the W3C version is published as HTML4 due to <a
href="http://www.w3.org/2005/07/pubrules?uimode=filter&uri=#format">W3C
- publication policies</a>.</li>
+ publication policies</a>.</li><!--HTML4POLICE-->
<li>The W3C version defines conformance for documents in a more
traditional (version-orientated) way, because of <a
@@ -143,11 +144,11 @@
not included in the W3C HTML5 specification, consist of:</p>
<ul class="brief">
- <li><a href="#2dcontext">Canvas 2D Graphics Context</a>
- <li><a href="#microdata">Microdata</a>
+ <li><a href="#2dcontext">Canvas 2D Graphics Context</a><!--2DCONTEXT-->
+ <li><a href="#microdata">Microdata</a><!--MD-->
<li><a href="#mdvocabs">Microdata vocabularies</a>
- <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)
- <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)
+ <li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)<!--POSTMSG-->
+ <li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)<!--POSTMSG-->
</ul>
<p>The <a href="#forms">forms</a> part of this specification was
@@ -456,7 +457,7 @@
type</span>, such as <code>text/html</code>, then it will be
processed as an HTML document by Web browsers.
- <!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+ <!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--VERSION-->
This specification defines version 5 of the HTML syntax, known as
"HTML5".
<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--END w3c-html--><!--VERSION-->
@@ -475,7 +476,7 @@
document labeled as XML from being rendered fully, whereas they
would be ignored in the HTML syntax.
- <!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+ <!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--VERSION-->
This specification defines version 5 of the XHTML syntax, known as
"XHTML5".
<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--END w3c-html--><!--VERSION-->
@@ -1535,7 +1536,7 @@
style.</p></blockquote></dd>
<!--(the following is not included in the WHATWG spec for quality reasons)-->
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--HPAAIG-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--HPAAIG--><!--FORK-->
<dt><cite>HTML to Platform Accessibility APIs Implementation Guide</cite> <a href="#refsHPAAIG">[HPAAIG]</a></dt>
<dd><blockquote><p>This is draft documentation mapping HTML
@@ -1544,7 +1545,7 @@
on deriving the accessible names and descriptions for HTML
elements. It also provides accessible feature implementation
examples.</p></blockquote></dd>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--HPAAIG-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--HPAAIG--><!--FORK-->
</dl>
@@ -1950,13 +1951,13 @@
because it is wrong. For example, content models are not syntax. It's
also unnecessary. What kinds of things are conformance requirements is
explained in the previous section, which talks about RFC 2119. -->
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--CONFORMANCE-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--CONFORMANCE--><!--FORK-->
<p class="note">the conformance requirements for documents include
syntax (the <table> element is conforming as a child of
<body>, but not as a child ot <title>), and semantics (the
<table> elements denotes a multi-dimensional data table, not a
piece of furniture).</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--CONFORMANCE-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--CONFORMANCE--><!--FORK-->
<p class="note impl">There is no implied relationship between
document conformance requirements and implementation conformance
@@ -2092,7 +2093,7 @@
"MUST" requirement because it has been proven to be impossible. <a
href="#refsCOMPUTABLE">[COMPUTABLE]</a>)</p>
- <!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+ <!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--VERSION-->
<p>The term "HTML5 validator" can be used to refer to a
conformance checker that itself conforms to the applicable
requirements of this specification.</p>
@@ -2656,7 +2657,7 @@
requirements in this specification. When someone applying this
specification to their activities decides that they will recognize
the requirements of such an extension specification, it becomes an
-<!--END w3c-html--><!--CONFORMANCE-->
+<!--END w3c-html--><!--CONFORMANCE--><!--FORK-->
<dfn title="other applicable specifications">applicable
specification</dfn> for the purposes of conformance requirements in
this specification.</p>
@@ -2670,7 +2671,7 @@
random junk is just that, junk, and not conforming at all. As far as
conformance goes, what matters in a particular community is what
that community <em>agrees</em> is applicable.</p>
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--CONFORMANCE-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--CONFORMANCE--><!--FORK-->
<!-- The following segment replaces the above in the W3C copy due to a
WG decision. The text is not included in the WHATWG version because
@@ -2690,7 +2691,7 @@
http://www.w3.org/mid/17E341CD-E790-422C-9F9A-69347EE01CEB@iki.fi
-->
-<!--START w3c-html--><!--CONFORMANCE-->
+<!--START w3c-html--><!--CONFORMANCE--><!--FORK-->
<dfn title="other applicable specifications">applicable
specification</dfn>.
@@ -2729,7 +2730,7 @@
element is NOT a <a href="#conforming-documents">conforming HTML5
document</a>, even if the element happens to be syntactically
correct HTML5.)</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--CONFORMANCE-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--CONFORMANCE--><!--FORK-->
<hr>
@@ -12281,7 +12282,7 @@
<div class="impl">
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!-- EDITORIAL: this paragraph is redundant with WAI-ARIA and doesn't really make any sense anyway; see bug 9437 -->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!-- EDITORIAL: this paragraph is redundant with WAI-ARIA and doesn't really make any sense anyway; see bug 9437 --><!--FORK-->
<p>The WAI-ARIA specification neither requires or forbids user
agents from enhancing native presentation and interaction behaviors
on the basis of WAI- ARIA markup. Even mainstream user agents might
@@ -12290,7 +12291,7 @@
fields or landmark navigation. User agents are encouraged to
maximize their usefulness to users, including users without
disabilities.</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!-- EDITORIAL -->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!-- EDITORIAL --><!--FORK-->
<p>Conformance checkers are encouraged to phrase errors such that
authors are encouraged to use more appropriate elements rather than
@@ -12709,9 +12710,9 @@
new instances of those objects. (This includes in particular the
<code>Window</code>, <code>Location</code>, <code>History</code>,
<code>ApplicationCache</code>,
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
<code>UndoManager</code>,
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
and <code>Navigator</code>, objects, the various
<code>BarProp</code> objects, the two <code>Storage</code> objects,
the various <code>HTMLCollection</code> objects, and objects
@@ -13907,10 +13908,10 @@
<p>A <code>link</code> element must have either a <code
title="attr-link-rel">rel</code> attribute, or an <code
title="attr-itemprop">itemprop</code> attribute, or both.</p>
-<!--START w3c-html--><!--MD--><!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+<!--START w3c-html--><!--MD--><!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--MD-->
<p>A <code>link</code> element must have <code
title="attr-link-rel">rel</code> attribute.</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--MD-->
<p>The types of link indicated (the relationships) are given by the
value of the <dfn title="attr-link-rel"><code>rel</code></dfn>
@@ -14354,8 +14355,7 @@
title="attr-itemprop">itemprop</code> is specified, then the <code
title="attr-meta-content">content</code> attribute must also be
specified. Otherwise, it must be omitted.</p>
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
-<!--START w3c-html--><!--MD-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--START w3c-html--><!--MD-->
<p>Exactly one of the <code title="attr-meta-name">name</code>,
<code title="attr-meta-http-equiv">http-equiv</code>, and <code
title="attr-meta-charset">charset</code> attributes must be
@@ -14365,7 +14365,7 @@
title="attr-meta-http-equiv">http-equiv</code> is specified, then
the <code title="attr-meta-content">content</code> attribute must
also be specified. Otherwise, it must be omitted.</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--WD-->
<p>The <dfn title="attr-meta-charset"><code>charset</code></dfn>
attribute specifies the character encoding used by the
@@ -23452,13 +23452,13 @@
display any image, or to prevent any image from being
displayed.
- <!--END w3c-html--><!--POLITICS-->
+ <!--END w3c-html--><!--POLITICS--><!--FORK-->
User agents may also apply heuristics to help the user make use of
the image when the user is unable to see it, e.g. due to a visual
disability or because they are using a text terminal with no
graphics capabilities. Such heuristics could include, for instance,
optical character recognition (OCR) of text found within the image.
- <!--START w3c-html--><!--POLITICS-->
+ <!--START w3c-html--><!--POLITICS--><!--FORK-->
</p>
@@ -24137,21 +24137,22 @@
scheme — the image should be specified in the site's CSS, not
in the markup of the document.</p>
-<!--END html--><!--END complete--><!--END epub--><!--END dev-html-->
+<!--END html--><!--END complete--><!--END epub--><!--END dev-html--><!--FORK-->
<p>Exceptions to this rule, in cases where CSS cannot be used to
display an entirely decorative image, are covered by the HTML5:
Techniques for providing useful text alternatives. <a href="#refsHTMLALTTECHS">[HTMLALTTECHS]</a>
Authors are also encouraged to consult the Web Content Accessibility
Guidelines 2.0 for more detailed information and acceptable
techniques. <a href="#refsWCAG">[WCAG]</a></p>
-<!--START html--><!--START complete--><!--START epub--><!--START dev-html-->
-<!--END w3c-html-->
+<!--START html--><!--START complete--><!--START epub--><!--START dev-html--><!--FORK-->
<!-- The above paragraph is omitted in the WHATWG copy and replaced
with the explicit requirement below because accessibility is better
served by having authors get all their information from one place,
instead of requiring them to read multiple (contradictory) documents. -->
+<!--END w3c-html--><!--FORK-->
+
<p>However, a decorative image that isn't discussed by the
surrounding text but still has some relevance can be included in a page
using the <code>img</code> element. Such images are decorative, but
@@ -24182,7 +24183,7 @@
</div>
-<!--START w3c-html-->
+<!--START w3c-html--><!--FORK-->
<h6>A group of images that form a single larger picture with no links</h6>
@@ -28132,19 +28133,19 @@
resource</span>.</p>
<p class="note">
- <!--END w3c-html-->
+ <!--END w3c-html--><!--FORK-->
Only the <span>MIME type</span> <!-- the WG decision started with the next bit, which is not in the style of the spec -->
- <!--START w3c-html-->
+ <!--START w3c-html--><!--FORK-->
"<code>application/octet-stream</code>"
- <!--END w3c-html-->
+ <!--END w3c-html--><!--FORK-->
with no parameters
- <!--START w3c-html-->
+ <!--START w3c-html--><!--FORK-->
is special-cased here; if any parameter appears with it, it
- <!--END w3c-html-->
+ <!--END w3c-html--><!--FORK-->
will <!-- the WG decision that led to this text had a "should", but this is a non-normative section -->
- <!--START w3c-html--><!--END html--><!--END complete--><!--END epub--><!--END dev-html-->
+ <!--START w3c-html--><!--END html--><!--END complete--><!--END epub--><!--END dev-html--><!--FORK-->
should
- <!--START html--><!--START complete--><!--START epub--><!--START dev-html-->
+ <!--START html--><!--START complete--><!--START epub--><!--START dev-html--><!--FORK-->
be treated just like any other <span>MIME type</span>.
This is a deviation from the rule <!-- in RFC 2046, section 1,
@@ -33680,7 +33681,7 @@
</div>
<!--KEEP-START w3c-html--><!--TT-->
-<!--END w3c-html--><!--TT-->
+<!--END w3c-html--><!--TTVTT-->
<!--START webvtt-->
<h5>WebVTT</h5>
@@ -35695,7 +35696,7 @@
<!--</div>-->
<!--END webvtt-->
-<!--START w3c-html--><!--TT-->
+<!--START w3c-html--><!--TTVTT-->
<h5>User interface</h5>
@@ -36520,9 +36521,9 @@
that element. When created, a <code>canvas</code> element must not
have a <span>primary context</span>.</p>
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!-- 2DCONTEXT -->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--2DCONTEXT-->
<p>The most commonly used primary context is the <a href="http://dev.w3.org/html5/2dcontext/">HTML Canvas 2D Context</a>.
-<!--START html--><!--START complete--><!--START epub--><!--START dev-html--><!-- 2DCONTEXT -->
+<!--START html--><!--START complete--><!--START epub--><!--START dev-html--><!--2DCONTEXT-->
<p>The <dfn title="dom-canvas-getContext"><code>getContext(<var
title="">contextId</var>, <var title="">args...</var>)</code></dfn>
@@ -41938,7 +41939,7 @@
the cell that corresponds to the values of the two dice.
</caption></pre>
-<!--END w3c-html--> <!-- HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) -->
+<!--END w3c-html--><!--HTML4POLICE (hidden in w3c version because w3c version has to be valid HTML4) --><!--FORK-->
<p>This provides the user with more context:</p>
<table class="dice-example">
@@ -41957,7 +41958,7 @@
<tr> <th> 5 <td> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11
<tr> <th> 6 <td> 7 <td> 8 <td> 9 <td> 10 <td> 11 <td> 12
</table>
-<!--START w3c-html-->
+<!--START w3c-html--><!--HTML4POLICE--><!--FORK-->
</div>
@@ -44151,7 +44152,7 @@
<td>29.0%
</table></pre>
-<!--END w3c-html--><!--HTML4POLICE-->
+<!--END w3c-html--><!--HTML4POLICE--><!--FORK-->
<p>This table could look like this:</p>
<table class="apple-table-examples e1">
@@ -44185,7 +44186,7 @@
<td>34.0%
<td>29.0%
</table>
-<!--START w3c-html--><!--HTML4POLICE-->
+<!--START w3c-html--><!--HTML4POLICE--><!--FORK-->
<hr>
@@ -61622,7 +61623,7 @@
<h3>Encoding microdata</h3>
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--MD-->
<p>The following attributes are added as <span>global
attributes</span> to <span>HTML elements</span>:</p>
@@ -61635,7 +61636,7 @@
<li><code title="attr-itemtype">itemtype</code></li>
</ul>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub-->
+<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--MD-->
<h4>The microdata model</h4>
@@ -62186,7 +62187,7 @@
<h3>Microdata DOM API</h3>
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub-->
+<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--MD-->
<pre class="idl">[Supplemental] interface <span>HTMLDocument</span> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
NodeList <span title="dom-document-getItems">getItems</span>(in optional DOMString typeNames); // <span>microdata</span>
};
@@ -62201,7 +62202,7 @@
readonly attribute <span>HTMLPropertiesCollection</span> <span title="dom-properties">properties</span>;
attribute any <span title="dom-itemValue">itemValue</span>;
};</pre>
-<!--START complete--><!--START epub--><!--START html--><!--START dev-html-->
+<!--START complete--><!--START epub--><!--START html--><!--START dev-html--><!--MD-->
<dl class="domintro">
@@ -62394,7 +62395,7 @@
-<!--END complete--><!--END epub--><!--END html--><!--END dev-html-->
+<!--END complete--><!--END epub--><!--END html--><!--END dev-html--><!--MD-->
<!--YYY
<h3>Other changes to HTML5</h3>
@@ -62441,7 +62442,7 @@
</div>
<!--END microdata-->
-<!--START complete--><!--START epub--><!--START html--><!--START dev-html-->
+<!--START complete--><!--START epub--><!--START html--><!--START dev-html--><!--MD-->
<h3 id="mdvocabs">Microdata vocabularies</h3>
@@ -67555,9 +67556,9 @@
attribute DOMString <span title="dom-name">name</span>; <!-- not [Replaceable] per WebKit and IE8 -->
[PutForwards=<span title="dom-location-href">href</span>] readonly attribute <span>Location</span> <span title="dom-location">location</span>;
readonly attribute <span>History</span> <span title="dom-history">history</span>;
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
readonly attribute <span>UndoManager</span> <span title="dom-undoManager">undoManager</span>;
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
[Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-locationbar">locationbar</span>;
[Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-menubar">menubar</span>;
[Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-personalbar">personalbar</span>;
@@ -80337,13 +80338,12 @@
</li>
-<!--END complete--><!--END epub--><!--END html--><!--END dev-html-->
-<!--START w3c-html--><!--MD-->
+<!--END complete--><!--END epub--><!--END html--><!--END dev-html--><!--START w3c-html--><!--MD-->
<li>Perform <dfn>drag-and-drop initialization steps</dfn> defined
in any <span>other applicable specifications</span>.</li>
-<!--START complete--><!--START epub--><!--START html--><!--START dev-html-->
+<!--START complete--><!--START epub--><!--START html--><!--START dev-html--><!--MD-->
<li>
@@ -81543,7 +81543,7 @@
</div>
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
<h3 id="undo"><dfn>Undo history</dfn></h3>
<div class="impl">
@@ -81922,7 +81922,7 @@
no detectable difference.</p>
</div>
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
@@ -82310,9 +82310,9 @@
transaction history</span>, restoring the associated state. If the
<span>undo position</span> is at the end of the <span>undo
transaction history</span>, the user agent must do nothing.
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
See the <span>undo history</span>.
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <span>undo position</span>
is not at the end of the <span>undo transaction
@@ -82376,9 +82376,9 @@
transaction history</span>, restoring the associated state. If the
<span>undo position</span> is at the start of the <span>undo
transaction history</span>, the user agent must do nothing.
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
See the <span>undo history</span>.
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
</dd>
<dd><strong>Enabled When</strong>: The <span>undo position</span>
is not at the start of the <span>undo transaction
@@ -82438,7 +82438,7 @@
"justifycenter", "justifyright", "justifyfull", "indent", "outdent"
-->
-<!--END w3c-html-->
+<!--END w3c-html--><!--PEERCONNECTION-->
<div data-component="other Hixie drafts (editor: Ian Hickson)">
<h2>Video conferencing and peer-to-peer communication</h2>
@@ -84459,7 +84459,8 @@
</div>
-<!--END html--><!--END dev-html-->
+<!--START w3c-html--><!--PEERCONNECTION-->
+<!--END html--><!--END dev-html--><!--END w3c-html-->
@@ -86228,7 +86229,8 @@
</div><!--data-component-->
-<!--START html--><!--START dev-html-->
+<!--START html--><!--START dev-html--><!--START w3c-html-->
+<!--END w3c-html--><!--POSTMSG-->
<h2 id="comms">Communication</h2>
@@ -86369,7 +86371,8 @@
</div><!--data-component-->
- <!--END html--><!--END dev-html-->
+<!--START w3c-html--><!--POSTMSG-->
+<!--END html--><!--END dev-html--><!--END w3c-html-->
<h3 id="server-sent-events"><dfn>Server-sent events</dfn></h3>
@@ -87781,11 +87784,11 @@
</div><!--data-component-->
- <!--START html--><!--START dev-html-->
+<!--START html--><!--START dev-html--><!--START w3c-html-->
+<!--END w3c-html--><!--POSTMSG-->
-
<div data-component="Web Messaging (editor: Ian Hickson)">
<!--START postmsg-->
@@ -88592,8 +88595,11 @@
</div><!--data-component-->
+<!--START w3c-html--><!--POSTMSG-->
+<!--END html--><!--END dev-html--><!--END w3c-html-->
-<!--END html--><!--END dev-html-->
+
+
<!--FIXUP complete -1-->
<div data-component="Web Storage (editor: Ian Hickson)">
@@ -89354,8 +89360,7 @@
-<!--START html--><!--START dev-html-->
-<!--START w3c-html-->
+<!--START html--><!--START dev-html--><!--START w3c-html-->
<h2 id="syntax"><dfn>The HTML syntax</dfn></h2>
@@ -106347,7 +106352,7 @@
<!--END microdata--><!--START w3c-html--><!--MD-->
-<!--END w3c-html-->
+<!--END w3c-html--><!--PEERCONNECTION-->
<h3><dfn><code>application/html-peer-connection-data</code></dfn></h3>
<p>This registration is for community review and will be submitted
@@ -106429,7 +106434,7 @@
<p>Fragment identifiers used with <code>text/html</code> resources
refer to <span>the indicated part of the document</span>.</p>
-<!--START w3c-html-->
+<!--START w3c-html--><!--PEERCONNECTION-->
<!--END w3c-html--><!--PING-->
@@ -110197,12 +110202,12 @@
<td> <code>Event</code>
<td> Fired at the <code>Document</code> when it finishes parsing and again when all its subresources have finished loading
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
<tr>
<td> <code title="event-redo">redo</code>
<td> <code>UndoManagerEvent</code>
<td> Fired at the <code>Window</code> object when the user <span title="do-redo">goes forward in the undo transaction history</span>
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
<tr>
<td> <code title="event-reset">reset</code>
@@ -110219,12 +110224,12 @@
<td> <code>Event</code>
<td> Fired at a <code>form</code> element when it is <span title="concept-form-submit">submitted</span>
-<!--END w3c-html-->
+<!--END w3c-html--><!--UNDO-->
<tr>
<td> <code title="event-undo">undo</code>
<td> <code>UndoManagerEvent</code>
<td> Fired at the <code>Window</code> object when the user <span title="do-undo">goes backward in the undo transaction history</span>
-<!--START w3c-html-->
+<!--START w3c-html--><!--UNDO-->
<tr>
<td> <code title="event-unload">unload</code>
@@ -111713,11 +111718,11 @@
features first widely deployed by the Windows Internet Explorer
browser.</p>
-<!--END w3c-html-->
+<!--END w3c-html--><!--MD-->
<p>Thanks to the participants of the microdata usability study for
allowing us to use their mistakes as a guide for designing the
microdata feature.</p>
-<!--START w3c-html-->
+<!--START w3c-html--><!--MD-->
<!--END w3c-html--><!--TT-->
<p>Thanks to the SubRip community, including in particular Zuggy and
More information about the Commit-Watchers
mailing list