[html5] r876 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-06-06 17:53:35 -0700 (Wed, 06 Jun 2007)
New Revision: 876

Modified:
   index
   source
Log:
[e] (0) So it seems that actually the last checkin might have been wrong. CRs get treated as LFs even as NCRs. What should we do?

Modified: index
===================================================================
--- index	2007-06-07 00:44:53 UTC (rev 875)
+++ index	2007-06-07 00:53:35 UTC (rev 876)
@@ -34661,13 +34661,12 @@
    backwards compatibility. If we do that we might be able to add more
    entities, e.g. for mathematics. Probably the way to mark whether or not an
    entity requires a semicolon is with an additional column in the <a
-   href="#entities0" title=entities>entity table lower down</a>.</p>
-  <!--
-XXX
-handle entities in the Win1252 range...
-http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/html/HTMLTokenizer.cpp#L101
-  -->
+   href="#entities0" title=entities>entity table lower down</a>.
 
+  <p class=big-issue>It seems browsers convert CRs to LFs even as entities.
+   Should we also do that? If so, we should remove the CRs in the tree
+   construction phase.
+
   <h4 id=tree-construction><span class=secno>8.2.4. </span><dfn
    id=tree-construction0>Tree construction</dfn></h4>
 

Modified: source
===================================================================
--- source	2007-06-07 00:44:53 UTC (rev 875)
+++ source	2007-06-07 00:53:35 UTC (rev 876)
@@ -32058,13 +32058,10 @@
   column in the <span title="entities">entity table lower
   down</span>.</p>
 
-  <!--
-XXX
-handle entities in the Win1252 range...
-http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/html/HTMLTokenizer.cpp#L101
-  -->
+  <p class="big-issue">It seems browsers convert CRs to LFs even as
+  entities. Should we also do that? If so, we should remove the CRs in
+  the tree construction phase.</p>
 
-
   <h4><dfn>Tree construction</dfn></h4>
 
   <p>The input to the tree construction stage is a sequence of tokens