[html5] r4839 - [e] (0) Mention that non-conforming markup results in non-conforming DOMs in an [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Mar 10 17:02:09 PST 2010
Author: ianh
Date: 2010-03-10 17:02:07 -0800 (Wed, 10 Mar 2010)
New Revision: 4839
Modified:
complete.html
index
source
Log:
[e] (0) Mention that non-conforming markup results in non-conforming DOMs in an example, by request.
Modified: complete.html
===================================================================
--- complete.html 2010-03-10 10:16:56 UTC (rev 4838)
+++ complete.html 2010-03-11 01:02:07 UTC (rev 4839)
@@ -157,7 +157,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Draft Standard — 10 March 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 11 March 2010</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>-->
@@ -77265,12 +77265,15 @@
<p class=example>In the non-conforming stream
<code><a href="a">a<table><a href="b">b</table>x</code>,
- the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing
- the second one, and the "x" character would be inside a link
- to "b", not to "a". This is despite the fact that the outer
- <code><a href=#the-a-element>a</a></code> element is not in table scope (meaning that a
- regular <code></a></code> end tag at the start of the table
- wouldn't close the outer <code><a href=#the-a-element>a</a></code> element).</p>
+ the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing the
+ second one, and the "x" character would be inside a link to "b",
+ not to "a". This is despite the fact that the outer <code><a href=#the-a-element>a</a></code>
+ element is not in table scope (meaning that a regular
+ <code></a></code> end tag at the start of the table wouldn't
+ close the outer <code><a href=#the-a-element>a</a></code> element). The result is that the
+ two <code><a href=#the-a-element>a</a></code> elements are indirectly nested inside each
+ other — non-conforming markup will often result in
+ non-conforming DOMs when parsed.</p>
<p><a href=#reconstruct-the-active-formatting-elements>Reconstruct the active formatting elements</a>, if
any.</p>
@@ -90858,6 +90861,7 @@
Rikkert Koppes,
Rimantas Liubertas,
Rob Ennals,
+ Rob Jellinghaus,
Robert Blaut,
Robert Collins,
Robert O'Callahan,
Modified: index
===================================================================
--- index 2010-03-10 10:16:56 UTC (rev 4838)
+++ index 2010-03-11 01:02:07 UTC (rev 4839)
@@ -161,7 +161,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1>
- <h2 class="no-num no-toc">Draft Standard — 10 March 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 11 March 2010</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>-->
@@ -70671,12 +70671,15 @@
<p class=example>In the non-conforming stream
<code><a href="a">a<table><a href="b">b</table>x</code>,
- the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing
- the second one, and the "x" character would be inside a link
- to "b", not to "a". This is despite the fact that the outer
- <code><a href=#the-a-element>a</a></code> element is not in table scope (meaning that a
- regular <code></a></code> end tag at the start of the table
- wouldn't close the outer <code><a href=#the-a-element>a</a></code> element).</p>
+ the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing the
+ second one, and the "x" character would be inside a link to "b",
+ not to "a". This is despite the fact that the outer <code><a href=#the-a-element>a</a></code>
+ element is not in table scope (meaning that a regular
+ <code></a></code> end tag at the start of the table wouldn't
+ close the outer <code><a href=#the-a-element>a</a></code> element). The result is that the
+ two <code><a href=#the-a-element>a</a></code> elements are indirectly nested inside each
+ other — non-conforming markup will often result in
+ non-conforming DOMs when parsed.</p>
<p><a href=#reconstruct-the-active-formatting-elements>Reconstruct the active formatting elements</a>, if
any.</p>
@@ -84419,6 +84422,7 @@
Rikkert Koppes,
Rimantas Liubertas,
Rob Ennals,
+ Rob Jellinghaus,
Robert Blaut,
Robert Collins,
Robert O'Callahan,
Modified: source
===================================================================
--- source 2010-03-10 10:16:56 UTC (rev 4838)
+++ source 2010-03-11 01:02:07 UTC (rev 4839)
@@ -88222,12 +88222,15 @@
<p class="example">In the non-conforming stream
<code><a href="a">a<table><a href="b">b</table>x</code>,
- the first <code>a</code> element would be closed upon seeing
- the second one, and the "x" character would be inside a link
- to "b", not to "a". This is despite the fact that the outer
- <code>a</code> element is not in table scope (meaning that a
- regular <code></a></code> end tag at the start of the table
- wouldn't close the outer <code>a</code> element).</p>
+ the first <code>a</code> element would be closed upon seeing the
+ second one, and the "x" character would be inside a link to "b",
+ not to "a". This is despite the fact that the outer <code>a</code>
+ element is not in table scope (meaning that a regular
+ <code></a></code> end tag at the start of the table wouldn't
+ close the outer <code>a</code> element). The result is that the
+ two <code>a</code> elements are indirectly nested inside each
+ other — non-conforming markup will often result in
+ non-conforming DOMs when parsed.</p>
<p><span>Reconstruct the active formatting elements</span>, if
any.</p>
@@ -101771,6 +101774,7 @@
Rikkert Koppes,
Rimantas Liubertas,
Rob Ennals,
+ Rob Jellinghaus,
Robert Blaut,
Robert Collins,
Robert O'Callahan,
More information about the Commit-Watchers
mailing list