html5/spec acknowledgements.html,1.877,1.878 infrastructure.html,1.880,1.881 spec.html,1.880,1.881 syntax.html,1.875,1.876

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv25209

Modified Files:
	acknowledgements.html infrastructure.html spec.html 
	syntax.html 
Log Message:
minor MIMESNIFf synchronisation (whatwg r4840)

[updated by splitter]


Index: infrastructure.html
===================================================================
RCS file: /sources/public/html5/spec/infrastructure.html,v
retrieving revision 1.880
retrieving revision 1.881
diff -u -d -r1.880 -r1.881
--- infrastructure.html	10 Mar 2010 02:46:36 -0000	1.880
+++ infrastructure.html	11 Mar 2010 04:56:33 -0000	1.881
@@ -3414,11 +3414,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="references.html#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="references.html#refsMIMESNIFF">[MIMESNIFF]</a></p>
+  specification for finding the <i>sniffed-type</i> of the relevant
+  sequence of octets. <a href="references.html#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:

Index: acknowledgements.html
===================================================================
RCS file: /sources/public/html5/spec/acknowledgements.html,v
retrieving revision 1.877
retrieving revision 1.878
diff -u -d -r1.877 -r1.878
--- acknowledgements.html	10 Mar 2010 02:46:36 -0000	1.877
+++ acknowledgements.html	11 Mar 2010 04:56:33 -0000	1.878
@@ -700,6 +700,7 @@
   Rikkert Koppes,
   Rimantas Liubertas,
   Rob Ennals,
+  Rob Jellinghaus,
   Robert Blaut,
   Robert Collins,
   Robert O'Callahan,

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.880
retrieving revision 1.881
diff -u -d -r1.880 -r1.881
--- spec.html	10 Mar 2010 10:26:30 -0000	1.880
+++ spec.html	11 Mar 2010 04:56:33 -0000	1.881
@@ -307,7 +307,7 @@
    </dl><p>This specification is available in the following formats: 
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>.
-This is revision 1.3875.
+This is revision 1.3877.
    </p> 
    <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide

Index: syntax.html
===================================================================
RCS file: /sources/public/html5/spec/syntax.html,v
retrieving revision 1.875
retrieving revision 1.876
diff -u -d -r1.875 -r1.876
--- syntax.html	9 Mar 2010 00:36:41 -0000	1.875
+++ syntax.html	11 Mar 2010 04:56:34 -0000	1.876
@@ -5804,12 +5804,15 @@
 
     <p class="example">In the non-conforming stream
     <code>&lt;a&#160;href="a"&gt;a&lt;table&gt;&lt;a&#160;href="b"&gt;b&lt;/table&gt;x</code>,
-    the first <code><a href="text-level-semantics.html#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="text-level-semantics.html#the-a-element">a</a></code> element is not in table scope (meaning that a
-    regular <code>&lt;/a&gt;</code> end tag at the start of the table
-    wouldn't close the outer <code><a href="text-level-semantics.html#the-a-element">a</a></code> element).</p>
+    the first <code><a href="text-level-semantics.html#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="text-level-semantics.html#the-a-element">a</a></code>
+    element is not in table scope (meaning that a regular
+    <code>&lt;/a&gt;</code> end tag at the start of the table wouldn't
+    close the outer <code><a href="text-level-semantics.html#the-a-element">a</a></code> element). The result is that the
+    two <code><a href="text-level-semantics.html#the-a-element">a</a></code> elements are indirectly nested inside each
+    other &#8212; 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>

Received on Thursday, 11 March 2010 04:56:38 UTC