- From: <bugzilla@jessica.w3.org>
- Date: Sat, 07 May 2011 20:39:18 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12297
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ian@hixie.ch
Resolution| |FIXED
--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-07 20:39:17 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: Partially Accepted
Change Description: see diff given below
Rationale: Added tab support.
Adding CR/CRLF support seems weird; this isn't a text format, and we don't do
special processing for CR anywhere else. Isn't the CR processing in the HTML
parser sufficient for this? If it's a real compat need then sure, but unless
there's a real compat need IMHO we shouldn't special-case CR here.
--
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 Saturday, 7 May 2011 20:39:20 UTC