This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 916 [details] test case for charset in single quotes <http://dev.w3.org/html5/spec/Overview.html#content-type-sniffing>: "Process the next character as follows: 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 treating single quotes as allowed quoting characters. The spec claims that this is required for "backwards compatibility with legacy content". I'm attaching a test case that shows that the following browsers do *not* treat single quotes as defined by the spec: IE6, IE8, IE9beta, Konqueror 4.4 Please remove the requirement.
(In reply to comment #0) > I'm attaching a test case that shows that the following browsers do *not* treat > single quotes as defined by the spec: > > IE6, IE8, IE9beta, Konqueror 4.4 (IE7 not tested)
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: Gecko, Opera, and WebKit all do this. If you want the spec to say something else, get them to change their browsers first. http://www.hixie.ch/tests/adhoc/html/parsing/encoding/075.html
(In reply to comment #2) > 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: Gecko, Opera, and WebKit all do this. If you want the spec to say > something else, get them to change their browsers first. > > http://www.hixie.ch/tests/adhoc/html/parsing/encoding/075.html Microsoft and KDE do it right. If you think the spec needs to overrule the base spec, please convince KDE and Microsoft to change their implementations. Will raise as tracker issue.
Now raised as http://www.w3.org/html/wg/tracker/issues/125
Working Group Decision: http://lists.w3.org/Archives/Public/public-html/2011Mar/0304.html
Please consider moving the text in question into a separate subsection; see proposal in <http://lists.w3.org/Archives/Public/public-html/2011Mar/0327.html>.
I assume comment 5 is asking for this change: "Instead of saying this is a willful violation of HTTP say this is a distinct algorithm from HTTP Content-Type processing for usage outside of HTTP." I applied comment 5 and comment 6.
Checked in as WHATWG revision r5979. Check-in comment: apply wg decision http://html5.org/tools/web-apps-tracker?from=5978&to=5979