- From: <bugzilla@jessica.w3.org>
- Date: Wed, 20 Jul 2011 14:30:16 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13309
Henri Sivonen <hsivonen@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |hsivonen@iki.fi
Resolution| |WORKSFORME
--- Comment #1 from Henri Sivonen <hsivonen@iki.fi> 2011-07-20 14:30:15 UTC ---
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 20 July 2011 14:30:21 UTC