[e] (0) Clarify the handling of CRLF in HTML.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=27413
Affected topics: HTML Syntax and Parsing

git-svn-id: https://svn.whatwg.org/webapps@8889 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -15449,7 +15449,7 @@ <h4 id=the-b-element>4.5.21 The <dfn><code>b</code></dfn> element</h4>
 
 
 
-  <h4 id=the-u-element>4.5.22 The <dfn><code>u</code></dfn> element</h4><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27409" title="<u> element examples">27409</a></div>
+  <h4 id=the-u-element>4.5.22 The <dfn><code>u</code></dfn> element</h4>
 
   <dl class=element><dt><a href=#concept-element-categories id=the-u-element:concept-element-categories>Categories</a>:<dd><a href=#flow-content-2 id=the-u-element:flow-content-2>Flow content</a>.<dd><a href=#phrasing-content-2 id=the-u-element:phrasing-content-2>Phrasing content</a>.<dd><a href=#palpable-content-2 id=the-u-element:palpable-content-2>Palpable content</a>.<dt><a href=#concept-element-contexts id=the-u-element:concept-element-contexts>Contexts in which this element can be used</a>:<dd>Where <a href=#phrasing-content-2 id=the-u-element:phrasing-content-2-2>phrasing content</a> is expected.<dt><a href=#concept-element-content-model id=the-u-element:concept-element-content-model>Content model</a>:<dd><a href=#phrasing-content-2 id=the-u-element:phrasing-content-2-3>Phrasing content</a>.<dt><a href=#concept-element-tag-omission id=the-u-element:concept-element-tag-omission>Tag omission in text/html</a>:<dd>Neither tag is omissible.<dt><a href=#concept-element-attributes id=the-u-element:concept-element-attributes>Content attributes</a>:<dd><a href=#global-attributes id=the-u-element:global-attributes>Global attributes</a><dt><a href=#concept-element-dom id=the-u-element:concept-element-dom>DOM interface</a>:<dd>Uses <code id=the-u-element:htmlelement><a href=#htmlelement>HTMLElement</a></code>.</dl>
 
@@ -72651,8 +72651,8 @@ <h5 id=preprocessing-the-input-stream>12.2.2.5 Preprocessing the input stream</h
   script APIs such as <code id=preprocessing-the-input-stream:dom-document-write><a href=#dom-document-write>document.write()</a></code>.)</p>
 
   <p>U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF) characters are treated
-  specially. All CR characters must be converted to LF characters, and any LF characters that
-  immediately follow a CR character must be ignored. Thus, newlines in HTML DOMs are represented by
+  specially. Any LF character that immediately follows a CR character must be ignored, and all CR
+  characters must then be converted to LF characters. Thus, newlines in HTML DOMs are represented by
   LF characters, and there are never any CR characters in the input to the <a href=#tokenization id=preprocessing-the-input-stream:tokenization>tokenization</a>
   stage.</p>
 

index

@@ -15449,7 +15449,7 @@ brighter. A &lt;b>rat&lt;/b> scurries past the corner wall.&lt;/p></pre>
 
 
 
-  <h4 id=the-u-element>4.5.22 The <dfn><code>u</code></dfn> element</h4><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27409" title="<u> element examples">27409</a></div>
+  <h4 id=the-u-element>4.5.22 The <dfn><code>u</code></dfn> element</h4>
 
   <dl class=element><dt><a href=#concept-element-categories id=the-u-element:concept-element-categories>Categories</a>:<dd><a href=#flow-content-2 id=the-u-element:flow-content-2>Flow content</a>.<dd><a href=#phrasing-content-2 id=the-u-element:phrasing-content-2>Phrasing content</a>.<dd><a href=#palpable-content-2 id=the-u-element:palpable-content-2>Palpable content</a>.<dt><a href=#concept-element-contexts id=the-u-element:concept-element-contexts>Contexts in which this element can be used</a>:<dd>Where <a href=#phrasing-content-2 id=the-u-element:phrasing-content-2-2>phrasing content</a> is expected.<dt><a href=#concept-element-content-model id=the-u-element:concept-element-content-model>Content model</a>:<dd><a href=#phrasing-content-2 id=the-u-element:phrasing-content-2-3>Phrasing content</a>.<dt><a href=#concept-element-tag-omission id=the-u-element:concept-element-tag-omission>Tag omission in text/html</a>:<dd>Neither tag is omissible.<dt><a href=#concept-element-attributes id=the-u-element:concept-element-attributes>Content attributes</a>:<dd><a href=#global-attributes id=the-u-element:global-attributes>Global attributes</a><dt><a href=#concept-element-dom id=the-u-element:concept-element-dom>DOM interface</a>:<dd>Uses <code id=the-u-element:htmlelement><a href=#htmlelement>HTMLElement</a></code>.</dl>
 
@@ -72651,8 +72651,8 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit
   script APIs such as <code id=preprocessing-the-input-stream:dom-document-write><a href=#dom-document-write>document.write()</a></code>.)</p>
 
   <p>U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF) characters are treated
-  specially. All CR characters must be converted to LF characters, and any LF characters that
-  immediately follow a CR character must be ignored. Thus, newlines in HTML DOMs are represented by
+  specially. Any LF character that immediately follows a CR character must be ignored, and all CR
+  characters must then be converted to LF characters. Thus, newlines in HTML DOMs are represented by
   LF characters, and there are never any CR characters in the input to the <a href=#tokenization id=preprocessing-the-input-stream:tokenization>tokenization</a>
   stage.</p>
 

source

@@ -97799,8 +97799,8 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   script APIs such as <code data-x="dom-document-write">document.write()</code>.)</p>
 
   <p>U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF) characters are treated
-  specially. All CR characters must be converted to LF characters, and any LF characters that
-  immediately follow a CR character must be ignored. Thus, newlines in HTML DOMs are represented by
+  specially. Any LF character that immediately follows a CR character must be ignored, and all CR
+  characters must then be converted to LF characters. Thus, newlines in HTML DOMs are represented by
   LF characters, and there are never any CR characters in the input to the <span>tokenization</span>
   stage.</p>