[Bug 10806] New: ignoring escapes is not needed for compatibility with existing content


           Summary: ignoring escapes is not needed for compatibility with
                    existing content
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/Overview.html#content-typ
        OS/Version: Windows NT
            Status: NEW
          Keywords: NE
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: julian.reschke@gmx.de
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
            Blocks: 10804


"If it is a U+0022 QUOTATION MARK ('"') and there is a later U+0022 QUOTATION
MARK ('"') in s
If it is a U+0027 APOSTROPHE ("'") and there is a later U+0027 APOSTROPHE ("'")
in s
    Return the encoding corresponding to the string between this character and
the next earliest occurrence of this character."

This is indeed a violation of the Content-Type syntax defined in RFC 2616, in
not handling backslash-escapes inside quoted-string properly.

The spec claims that this is required for "backwards compatibility with legacy

I'm attaching a test case that shows that the following browsers *do* handle
escapes despite what the spec says:

Opera, Safari, Konqueror 4.4

Please remove the requirement to violate the base syntax.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Wednesday, 29 September 2010 11:45:59 UTC