13309 2011-07-20 12:08:37 +0000 HTML and XHTML handle newline differently 2011-08-09 23:17:46 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX P2 normal --- 1 peaceable_whale ian bzbarsky hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51316 0 peaceable_whale 2011-07-20 12:08:37 +0000 text/html and application/xhtml+xml documents currently have 2 different newline handling rules, causing inconsistent rendering even when the markup is the same. The rule for text/html ignores character reference of U+000D CARRIAGE RETURN (Section 8.1.3.1 of HTML 5 spec) while the rule for application/xhtml document translates both the two-character sequence #xD #xA and any #xD that is not followed by #xA to a single #xA character. (Section 2.11 of XML spec). Should HTML 5 follow the handling rule of XML? 51320 1 hsivonen 2011-07-20 14:30:15 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: The spec already says what is requested Change Description: no spec change Rationale: HTML5 doesn't ignore carriage returns. Lone literal carriage returns turn into line feeds. So does the CRLF pair. An escaped carriage return ends up in the DOM as a carriage return. Just like in XML. I don't know which particular passage or sentence in which particular publication you are referring to, so I can't comment on the exact text that made it seem as though this wasn't already the case. For future bugs: Please avoid referring to the section numbers of the HTML5 spec. The numbering changes all the time and differs between different views and publication venues of HTML5. In the future, please use a URL with a fragment id part to refer to a section of the spec. 51321 2 peaceable_whale 2011-07-20 14:34:59 +0000 Under Section 8.1.3.1 of HTML 5: "Where character references are allowed, a character reference of a U+000A LINE FEED (LF) character (but not a U+000D CARRIAGE RETURN (CR) character) also represents a newline." In other words, 
 is ignored. I will upload some browser test results to this report soon. 51322 3 1013 peaceable_whale 2011-07-20 14:36:45 +0000 Created attachment 1013 text/html test document 51323 4 1014 peaceable_whale 2011-07-20 14:37:23 +0000 Created attachment 1014 application/xhtml+xml test document 51324 5 1015 peaceable_whale 2011-07-20 14:39:27 +0000 Created attachment 1015 Firefox 5 and Chrome 12 output of both HTML and XHTML documents 51325 6 1016 peaceable_whale 2011-07-20 14:39:51 +0000 Created attachment 1016 IE 9 output of text/html document 51326 7 1017 peaceable_whale 2011-07-20 14:40:35 +0000 Created attachment 1017 IE 9 output of application/xhtml+xml document and Opera output for both HTML and XHTML 51327 8 peaceable_whale 2011-07-20 14:43:11 +0000 IE 9's text/html output is buggy while application/xhtml+xml output follows XML spec. Firefox and Chrome use HTML 5's handling regardless of media type. Opera uses XML spec's handling regardless of media type. 52435 9 mike 2011-08-04 05:01:27 +0000 mass-moved component to LC1 54497 10 ian 2011-08-09 23:17:46 +0000 (In reply to comment #2) > Under Section 8.1.3.1 of HTML 5: > > "Where character references are allowed, a character reference of a U+000A LINE > FEED (LF) character (but not a U+000D CARRIAGE RETURN (CR) character) also > represents a newline." > > In other words, 
 is ignored. No, what you quote is not at all saying that 
 is ignored. It's saying that if you want to represent a newline, you can use 
, but not 
. If you read the parser section, you'll see 
 turns into a U+000D character, which doesn't represent anything useful in HTML. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Spec is as intended. 1013 2011-07-20 14:36:45 +0000 2011-07-20 14:36:45 +0000 text/html test document linebreak-test.html text/html 390 peaceable_whale PCFET0NUWVBFIGh0bWw+DQo8aHRtbCB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94aHRt bCI+DQo8aGVhZD4NCjxtZXRhIGNoYXJzZXQ9IlVURi04IiAvPg0KPHRpdGxlPkxpbmUgQnJlYWsg Q2hhcmFjdGVyIFJlZmVyZW5jZSBUZXN0PC90aXRsZT4NCjwvaGVhZD4NCjxib2R5Pg0KPHByZT5M aW5lIDEmI3gwQTtMaW5lIDImI3gwRDtMaW5lIDMmI3gwRDsmI3gwQTtMaW5lIDQmI3gwQTsmI3gw RDtMaW5lIDYmI3gwQTsmI3gwRDsmI3gwQTtMaW5lIDgmI3gwRDsmI3gwRDsmI3gwQTtMaW5lIDEw JiN4MEQ7JiN4MEE7JiN4MEQ7TGluZSAxMiYjeDBEOyYjeDBBOyYjeDBBO0xpbmUgMTQmI3gwRDsm I3gwQTsmI3gwRDsmI3gwQTtMaW5lIDE2PC9wcmU+DQo8L2JvZHk+DQo8L2h0bWw+ 1014 2011-07-20 14:37:23 +0000 2011-07-20 14:37:23 +0000 application/xhtml+xml test document linebreak-test.xhtml application/xhtml+xml 390 peaceable_whale PCFET0NUWVBFIGh0bWw+DQo8aHRtbCB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94aHRt bCI+DQo8aGVhZD4NCjxtZXRhIGNoYXJzZXQ9IlVURi04IiAvPg0KPHRpdGxlPkxpbmUgQnJlYWsg Q2hhcmFjdGVyIFJlZmVyZW5jZSBUZXN0PC90aXRsZT4NCjwvaGVhZD4NCjxib2R5Pg0KPHByZT5M aW5lIDEmI3gwQTtMaW5lIDImI3gwRDtMaW5lIDMmI3gwRDsmI3gwQTtMaW5lIDQmI3gwQTsmI3gw RDtMaW5lIDYmI3gwQTsmI3gwRDsmI3gwQTtMaW5lIDgmI3gwRDsmI3gwRDsmI3gwQTtMaW5lIDEw JiN4MEQ7JiN4MEE7JiN4MEQ7TGluZSAxMiYjeDBEOyYjeDBBOyYjeDBBO0xpbmUgMTQmI3gwRDsm I3gwQTsmI3gwRDsmI3gwQTtMaW5lIDE2PC9wcmU+DQo8L2JvZHk+DQo8L2h0bWw+ 1015 2011-07-20 14:39:27 +0000 2011-07-20 14:41:48 +0000 Firefox 5 and Chrome 12 output of both HTML and XHTML documents firefox+chrome_result.txt text/plain 86 peaceable_whale TGluZSAxDQpMaW5lIDJMaW5lIDMNCkxpbmUgNA0KTGluZSA2DQoNCkxpbmUgOA0KTGluZSAxMA0K TGluZSAxMg0KDQpMaW5lIDE0DQoNCkxpbmUgMTY= 1016 2011-07-20 14:39:51 +0000 2011-07-20 14:39:51 +0000 IE 9 output of text/html document ie9html_result.txt text/plain 108 peaceable_whale TGluZSAxDQpMaW5lIDINCkxpbmUgMw0KDQpMaW5lIDQNCg0KTGluZSA2DQoNCg0KTGluZSA4DQoN Cg0KTGluZSAxMA0KDQoNCkxpbmUgMTINCg0KDQpMaW5lIDE0DQoNCg0KDQpMaW5lIDE2 1017 2011-07-20 14:40:35 +0000 2011-07-20 14:40:35 +0000 IE 9 output of application/xhtml+xml document and Opera output for both HTML and XHTML ie9xhtml+opera_result.txt text/plain 94 peaceable_whale TGluZSAxDQpMaW5lIDINCkxpbmUgMw0KTGluZSA0DQoNCkxpbmUgNg0KDQpMaW5lIDgNCg0KTGlu ZSAxMA0KDQpMaW5lIDEyDQoNCkxpbmUgMTQNCg0KTGluZSAxNg==