[html5] Commit-Watchers Digest, Vol 35, Issue 11
Omid Ashtari
oashtari at gmail.com
Thu Mar 11 12:00:09 PST 2010
will you please unsubscribe me - thanks
On Thu, Mar 11, 2010 at 12:01 PM,
<commit-watchers-request at lists.whatwg.org>wrote:
> Send Commit-Watchers mailing list submissions to
> commit-watchers at lists.whatwg.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
> or, via email, send a message with subject or body 'help' to
> commit-watchers-request at lists.whatwg.org
>
> You can reach the person managing the list at
> commit-watchers-owner at lists.whatwg.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Commit-Watchers digest..."
>
>
> Today's Topics:
>
> 1. r4839 - [e] (0) Mention that non-conforming markup results
> in non-conforming DOMs in an [...] (whatwg at whatwg.org)
> 2. r4840 - [e] (0) minor MIMESNIFf synchronisation
> (whatwg at whatwg.org)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 10 Mar 2010 17:02:09 -0800 (PST)
> From: whatwg at whatwg.org
> To: commit-watchers at whatwg.org
> Subject: [html5] r4839 - [e] (0) Mention that non-conforming markup
> results in non-conforming DOMs in an [...]
> Message-ID: <20100311010209.D4597805818C at ps20323.dreamhostps.com>
> Content-Type: text/plain; charset=UTF-8
>
> 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,
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 10 Mar 2010 20:46:56 -0800 (PST)
> From: whatwg at whatwg.org
> To: commit-watchers at whatwg.org
> Subject: [html5] r4840 - [e] (0) minor MIMESNIFf synchronisation
> Message-ID: <20100311044656.F2F6A805818C at ps20323.dreamhostps.com>
> Content-Type: text/plain; charset=UTF-8
>
> Author: ianh
> Date: 2010-03-10 20:46:55 -0800 (Wed, 10 Mar 2010)
> New Revision: 4840
>
> Modified:
> complete.html
> index
> source
> Log:
> [e] (0) minor MIMESNIFf synchronisation
>
> Modified: complete.html
> ===================================================================
> --- complete.html 2010-03-11 01:02:07 UTC (rev 4839)
> +++ complete.html 2010-03-11 04:46:55 UTC (rev 4840)
> @@ -5471,11 +5471,13 @@
> Content-Type</dfn>, given a string <var title="">s</var>, is given
> in the Content-Type Processing Model specification. It either
> returns an encoding or nothing. <a
> href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
> + <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>
>
> <p>The <dfn id=content-type-sniffing-0 title="Content-Type
> sniffing">sniffed type of a
> resource</dfn> must be found in a manner consistent with the
> requirements given in the Content-Type Processing Model
> - specification for finding that <i>sniffed type</i>. <a
> href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
> + specification for finding the <i>sniffed-type</i> of the relevant
> + sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
>
> <p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing:
> image">rules for sniffing
> images specifically</dfn> and the <dfn
> id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
>
> Modified: index
> ===================================================================
> --- index 2010-03-11 01:02:07 UTC (rev 4839)
> +++ index 2010-03-11 04:46:55 UTC (rev 4840)
> @@ -5370,11 +5370,13 @@
> Content-Type</dfn>, given a string <var title="">s</var>, is given
> in the Content-Type Processing Model specification. It either
> returns an encoding or nothing. <a
> href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
> + <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>
>
> <p>The <dfn id=content-type-sniffing-0 title="Content-Type
> sniffing">sniffed type of a
> resource</dfn> must be found in a manner consistent with the
> requirements given in the Content-Type Processing Model
> - specification for finding that <i>sniffed type</i>. <a
> href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
> + specification for finding the <i>sniffed-type</i> of the relevant
> + sequence of octets. <a href=#refsMIMESNIFF>[MIMESNIFF]</a></p>
>
> <p>The <dfn id=content-type-sniffing:-image title="Content-Type sniffing:
> image">rules for sniffing
> images specifically</dfn> and the <dfn
> id=content-type-sniffing:-text-or-binary title="Content-Type sniffing:
>
> Modified: source
> ===================================================================
> --- source 2010-03-11 01:02:07 UTC (rev 4839)
> +++ source 2010-03-11 04:46:55 UTC (rev 4840)
> @@ -5021,12 +5021,13 @@
> in the Content-Type Processing Model specification. It either
> returns an encoding or nothing. <a
> href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
> + <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>
>
> <p>The <dfn title="Content-Type sniffing">sniffed type of a
> resource</dfn> must be found in a manner consistent with the
> requirements given in the Content-Type Processing Model
> - specification for finding that <i>sniffed type</i>. <a
> - href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
> + specification for finding the <i>sniffed-type</i> of the relevant
> + sequence of octets. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
>
> <p>The <dfn title="Content-Type sniffing: image">rules for sniffing
> images specifically</dfn> and the <dfn title="Content-Type sniffing:
>
>
>
> ------------------------------
>
> _______________________________________________
> Commit-Watchers mailing list
> Commit-Watchers at lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
>
>
> End of Commit-Watchers Digest, Vol 35, Issue 11
> ***********************************************
>
--
Omid Ashtari
C10, Partner
310-346-3191
oashtari at gmail.com
@oashtari
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/commit-watchers-whatwg.org/attachments/20100311/993c0005/attachment-0002.htm>
More information about the Commit-Watchers
mailing list