W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2010

[Bug 9144] New: 
 should expand to CR

From: <bugzilla@wiggum.w3.org>
Date: Thu, 25 Feb 2010 10:33:15 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9144-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9144

           Summary: &#13; should expand to CR
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Spec rev. 942 made &#13; expand to LF.
http://html5.org/tools/web-apps-tracker?from=941&to=942

The top 4 browser engines expand it to CR.
http://hsivonen.iki.fi/test/moz/escaped-crlf.html

Mozilla has at least one test case that expects the expansion to CR, although
the test case is not based on a real-world site.

This is also a gratuitous difference between text/html and XML, see:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-June/011703.html

Given the legacy text/html behavior and the XML behavior, I think it's not
worthwhile to map &#13; to LF and risk the change causing any compat issues,
even though I have no evidence of Web compat issues here.

Please revert rev 942 (I'm OK with making &#13; a parse error, though).

Note: Please don't make a CR expanded from &#13; followed by an LF coalesce
into an LF like a literal CRLF sequence.


-- 
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 Thursday, 25 February 2010 10:33:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:12 UTC