will you please unsubscribe me - thanks<br><br><div class="gmail_quote">On Thu, Mar 11, 2010 at 12:01 PM, <span dir="ltr"><<a href="mailto:commit-watchers-request@lists.whatwg.org">commit-watchers-request@lists.whatwg.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Send Commit-Watchers mailing list submissions to<br>
<a href="mailto:commit-watchers@lists.whatwg.org">commit-watchers@lists.whatwg.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:commit-watchers-request@lists.whatwg.org">commit-watchers-request@lists.whatwg.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:commit-watchers-owner@lists.whatwg.org">commit-watchers-owner@lists.whatwg.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Commit-Watchers digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. r4839 - [e] (0) Mention that non-conforming markup results<br>
in non-conforming DOMs in an [...] (<a href="mailto:whatwg@whatwg.org">whatwg@whatwg.org</a>)<br>
2. r4840 - [e] (0) minor MIMESNIFf synchronisation<br>
(<a href="mailto:whatwg@whatwg.org">whatwg@whatwg.org</a>)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 10 Mar 2010 17:02:09 -0800 (PST)<br>
From: <a href="mailto:whatwg@whatwg.org">whatwg@whatwg.org</a><br>
To: <a href="mailto:commit-watchers@whatwg.org">commit-watchers@whatwg.org</a><br>
Subject: [html5] r4839 - [e] (0) Mention that non-conforming markup<br>
results in non-conforming DOMs in an [...]<br>
Message-ID: <<a href="mailto:20100311010209.D4597805818C@ps20323.dreamhostps.com">20100311010209.D4597805818C@ps20323.dreamhostps.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Author: ianh<br>
Date: 2010-03-10 17:02:07 -0800 (Wed, 10 Mar 2010)<br>
New Revision: 4839<br>
<br>
Modified:<br>
complete.html<br>
index<br>
source<br>
Log:<br>
[e] (0) Mention that non-conforming markup results in non-conforming DOMs in an example, by request.<br>
<br>
Modified: complete.html<br>
===================================================================<br>
--- complete.html 2010-03-10 10:16:56 UTC (rev 4838)<br>
+++ complete.html 2010-03-11 01:02:07 UTC (rev 4839)<br>
@@ -157,7 +157,7 @@<br>
<br>
<header class=head id=head><p><a class=logo href=<a href="http://www.whatwg.org/" target="_blank">http://www.whatwg.org/</a> rel=home><img alt=WHATWG src=/images/logo></a></p><br>
<hgroup><h1>Web Applications 1.0</h1><br>
- <h2 class="no-num no-toc">Draft Standard &mdash; 10 March 2010</h2><br>
+ <h2 class="no-num no-toc">Draft Standard &mdash; 11 March 2010</h2><br>
</hgroup><p>You can take part in this work. <a href=<a href="http://www.whatwg.org/mailing-list" target="_blank">http://www.whatwg.org/mailing-list</a>>Join the working group's discussion list.</a></p><br>
<p><strong>Web designers!</strong> We have a <a href=<a href="http://blog.whatwg.org/faq/" target="_blank">http://blog.whatwg.org/faq/</a>>FAQ</a>, a <a href=<a href="http://forums.whatwg.org/" target="_blank">http://forums.whatwg.org/</a>>forum</a>, and a <a href=<a href="http://www.whatwg.org/mailing-list#help" target="_blank">http://www.whatwg.org/mailing-list#help</a>>help mailing list</a> for you!</p><br>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="<a href="http://www.whatwg.org/mailing-list#implementors" target="_blank">http://www.whatwg.org/mailing-list#implementors</a>">mailing list</a> for you too!</p>--><br>
@@ -77265,12 +77265,15 @@<br>
<br>
<p class=example>In the non-conforming stream<br>
<code>&lt;a&nbsp;href="a"&gt;a&lt;table&gt;&lt;a&nbsp;href="b"&gt;b&lt;/table&gt;x</code>,<br>
- the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing<br>
- the second one, and the "x" character would be inside a link<br>
- to "b", not to "a". This is despite the fact that the outer<br>
- <code><a href=#the-a-element>a</a></code> element is not in table scope (meaning that a<br>
- regular <code>&lt;/a&gt;</code> end tag at the start of the table<br>
- wouldn't close the outer <code><a href=#the-a-element>a</a></code> element).</p><br>
+ the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing the<br>
+ second one, and the "x" character would be inside a link to "b",<br>
+ not to "a". This is despite the fact that the outer <code><a href=#the-a-element>a</a></code><br>
+ element is not in table scope (meaning that a regular<br>
+ <code>&lt;/a&gt;</code> end tag at the start of the table wouldn't<br>
+ close the outer <code><a href=#the-a-element>a</a></code> element). The result is that the<br>
+ two <code><a href=#the-a-element>a</a></code> elements are indirectly nested inside each<br>
+ other &mdash; non-conforming markup will often result in<br>
+ non-conforming DOMs when parsed.</p><br>
<br>
<p><a href=#reconstruct-the-active-formatting-elements>Reconstruct the active formatting elements</a>, if<br>
any.</p><br>
@@ -90858,6 +90861,7 @@<br>
Rikkert Koppes,<br>
Rimantas Liubertas,<br>
Rob Ennals,<br>
+ Rob Jellinghaus,<br>
Robert Blaut,<br>
Robert Collins,<br>
Robert O'Callahan,<br>
<br>
Modified: index<br>
===================================================================<br>
--- index 2010-03-10 10:16:56 UTC (rev 4838)<br>
+++ index 2010-03-11 01:02:07 UTC (rev 4839)<br>
@@ -161,7 +161,7 @@<br>
<br>
<header class=head id=head><p><a class=logo href=<a href="http://www.whatwg.org/" target="_blank">http://www.whatwg.org/</a> rel=home><img alt=WHATWG src=/images/logo></a></p><br>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1><br>
- <h2 class="no-num no-toc">Draft Standard &mdash; 10 March 2010</h2><br>
+ <h2 class="no-num no-toc">Draft Standard &mdash; 11 March 2010</h2><br>
</hgroup><p>You can take part in this work. <a href=<a href="http://www.whatwg.org/mailing-list" target="_blank">http://www.whatwg.org/mailing-list</a>>Join the working group's discussion list.</a></p><br>
<p><strong>Web designers!</strong> We have a <a href=<a href="http://blog.whatwg.org/faq/" target="_blank">http://blog.whatwg.org/faq/</a>>FAQ</a>, a <a href=<a href="http://forums.whatwg.org/" target="_blank">http://forums.whatwg.org/</a>>forum</a>, and a <a href=<a href="http://www.whatwg.org/mailing-list#help" target="_blank">http://www.whatwg.org/mailing-list#help</a>>help mailing list</a> for you!</p><br>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="<a href="http://www.whatwg.org/mailing-list#implementors" target="_blank">http://www.whatwg.org/mailing-list#implementors</a>">mailing list</a> for you too!</p>--><br>
@@ -70671,12 +70671,15 @@<br>
<br>
<p class=example>In the non-conforming stream<br>
<code>&lt;a&nbsp;href="a"&gt;a&lt;table&gt;&lt;a&nbsp;href="b"&gt;b&lt;/table&gt;x</code>,<br>
- the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing<br>
- the second one, and the "x" character would be inside a link<br>
- to "b", not to "a". This is despite the fact that the outer<br>
- <code><a href=#the-a-element>a</a></code> element is not in table scope (meaning that a<br>
- regular <code>&lt;/a&gt;</code> end tag at the start of the table<br>
- wouldn't close the outer <code><a href=#the-a-element>a</a></code> element).</p><br>
+ the first <code><a href=#the-a-element>a</a></code> element would be closed upon seeing the<br>
+ second one, and the "x" character would be inside a link to "b",<br>
+ not to "a". This is despite the fact that the outer <code><a href=#the-a-element>a</a></code><br>
+ element is not in table scope (meaning that a regular<br>
+ <code>&lt;/a&gt;</code> end tag at the start of the table wouldn't<br>
+ close the outer <code><a href=#the-a-element>a</a></code> element). The result is that the<br>
+ two <code><a href=#the-a-element>a</a></code> elements are indirectly nested inside each<br>
+ other &mdash; non-conforming markup will often result in<br>
+ non-conforming DOMs when parsed.</p><br>
<br>
<p><a href=#reconstruct-the-active-formatting-elements>Reconstruct the active formatting elements</a>, if<br>
any.</p><br>
@@ -84419,6 +84422,7 @@<br>
Rikkert Koppes,<br>
Rimantas Liubertas,<br>
Rob Ennals,<br>
+ Rob Jellinghaus,<br>
Robert Blaut,<br>
Robert Collins,<br>
Robert O'Callahan,<br>
<br>
Modified: source<br>
===================================================================<br>
--- source 2010-03-10 10:16:56 UTC (rev 4838)<br>
+++ source 2010-03-11 01:02:07 UTC (rev 4839)<br>
@@ -88222,12 +88222,15 @@<br>
<br>
<p class="example">In the non-conforming stream<br>
<code>&lt;a&nbsp;href="a">a&lt;table>&lt;a&nbsp;href="b">b&lt;/table>x</code>,<br>
- the first <code>a</code> element would be closed upon seeing<br>
- the second one, and the "x" character would be inside a link<br>
- to "b", not to "a". This is despite the fact that the outer<br>
- <code>a</code> element is not in table scope (meaning that a<br>
- regular <code>&lt;/a></code> end tag at the start of the table<br>
- wouldn't close the outer <code>a</code> element).</p><br>
+ the first <code>a</code> element would be closed upon seeing the<br>
+ second one, and the "x" character would be inside a link to "b",<br>
+ not to "a". This is despite the fact that the outer <code>a</code><br>
+ element is not in table scope (meaning that a regular<br>
+ <code>&lt;/a></code> end tag at the start of the table wouldn't<br>
+ close the outer <code>a</code> element). The result is that the<br>
+ two <code>a</code> elements are indirectly nested inside each<br>
+ other &mdash; non-conforming markup will often result in<br>
+ non-conforming DOMs when parsed.</p><br>
<br>
<p><span>Reconstruct the active formatting elements</span>, if<br>
any.</p><br>
@@ -101771,6 +101774,7 @@<br>
Rikkert Koppes,<br>
Rimantas Liubertas,<br>
Rob Ennals,<br>
+ Rob Jellinghaus,<br>
Robert Blaut,<br>
Robert Collins,<br>
Robert O'Callahan,<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 10 Mar 2010 20:46:56 -0800 (PST)<br>
From: <a href="mailto:whatwg@whatwg.org">whatwg@whatwg.org</a><br>
To: <a href="mailto:commit-watchers@whatwg.org">commit-watchers@whatwg.org</a><br>
Subject: [html5] r4840 - [e] (0) minor MIMESNIFf synchronisation<br>
Message-ID: <<a href="mailto:20100311044656.F2F6A805818C@ps20323.dreamhostps.com">20100311044656.F2F6A805818C@ps20323.dreamhostps.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Author: ianh<br>
Date: 2010-03-10 20:46:55 -0800 (Wed, 10 Mar 2010)<br>
New Revision: 4840<br>
<br>
Modified:<br>
complete.html<br>
index<br>
source<br>
Log:<br>
[e] (0) minor MIMESNIFf synchronisation<br>
<br>
Modified: complete.html<br>
===================================================================<br>
--- complete.html 2010-03-11 01:02:07 UTC (rev 4839)<br>
+++ complete.html 2010-03-11 04:46:55 UTC (rev 4840)<br>
@@ -5471,11 +5471,13 @@<br>
Content-Type</dfn>, given a string <var title="">s</var>, is given<br>
in the Content-Type Processing Model specification. It either<br>
returns an encoding or nothing. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
+ <p class=XXX>The above is out of date now that the relevant section has been removed from MIMESNIFF. Stay tuned; I'll bring it back here soon.</p><br>
<br>
<p>The <dfn id=content-type-sniffing-0 title="Content-Type sniffing">sniffed type of a<br>
resource</dfn> must be found in a manner consistent with the<br>
requirements given in the Content-Type Processing Model<br>
- specification for finding that <i>sniffed type</i>. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
+ specification for finding the <i>sniffed-type</i> of the relevant<br>
+ sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
<br>
<p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing<br>
images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:<br>
<br>
Modified: index<br>
===================================================================<br>
--- index 2010-03-11 01:02:07 UTC (rev 4839)<br>
+++ index 2010-03-11 04:46:55 UTC (rev 4840)<br>
@@ -5370,11 +5370,13 @@<br>
Content-Type</dfn>, given a string <var title="">s</var>, is given<br>
in the Content-Type Processing Model specification. It either<br>
returns an encoding or nothing. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
+ <p class=XXX>The above is out of date now that the relevant section has been removed from MIMESNIFF. Stay tuned; I'll bring it back here soon.</p><br>
<br>
<p>The <dfn id=content-type-sniffing-0 title="Content-Type sniffing">sniffed type of a<br>
resource</dfn> must be found in a manner consistent with the<br>
requirements given in the Content-Type Processing Model<br>
- specification for finding that <i>sniffed type</i>. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
+ specification for finding the <i>sniffed-type</i> of the relevant<br>
+ sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p><br>
<br>
<p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing: image">rules for sniffing<br>
images specifically</dfn> and the <dfn id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:<br>
<br>
Modified: source<br>
===================================================================<br>
--- source 2010-03-11 01:02:07 UTC (rev 4839)<br>
+++ source 2010-03-11 04:46:55 UTC (rev 4840)<br>
@@ -5021,12 +5021,13 @@<br>
in the Content-Type Processing Model specification. It either<br>
returns an encoding or nothing. <a<br>
href="#refsMIMESNIFF">[MIMESNIFF]</a></p><br>
+ <p class="XXX">The above is out of date now that the relevant section has been removed from MIMESNIFF. Stay tuned; I'll bring it back here soon.</p><br>
<br>
<p>The <dfn title="Content-Type sniffing">sniffed type of a<br>
resource</dfn> must be found in a manner consistent with the<br>
requirements given in the Content-Type Processing Model<br>
- specification for finding that <i>sniffed type</i>. <a<br>
- href="#refsMIMESNIFF">[MIMESNIFF]</a></p><br>
+ specification for finding the <i>sniffed-type</i> of the relevant<br>
+ sequence of octets. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p><br>
<br>
<p>The <dfn title="Content-Type sniffing: image">rules for sniffing<br>
images specifically</dfn> and the <dfn title="Content-Type sniffing:<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Commit-Watchers mailing list<br>
<a href="mailto:Commit-Watchers@lists.whatwg.org">Commit-Watchers@lists.whatwg.org</a><br>
<a href="http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org" target="_blank">http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org</a><br>
<br>
<br>
End of Commit-Watchers Digest, Vol 35, Issue 11<br>
***********************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Omid Ashtari<br>C10, Partner<br>310-346-3191<br><a href="mailto:oashtari@gmail.com">oashtari@gmail.com</a><br>@oashtari<br><br>