- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Sep 2010 11:30:11 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10804 Summary: charset sniffing: please describe the incompatibility Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW 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, public-html@w3.org >From <http://dev.w3.org/html5/spec/Overview.html#content-type-sniffing>: "This requirement is a willful violation of the HTTP specification, motivated by the need for backwards compatibility with legacy content. [HTTP]" It would be a service to the reader to actually state what the willful violation is. Now, with the problem described in <http://www.w3.org/Bugs/Public/show_bug.cgi?id=9628#c1> being fixed, I see still two of them: - the spec allows single quotes instead of double quotes - the spec doesn't handle escapes I'll show in two separate bugs that both violations are *not* widely implemented, thus apparently not required for "legacy content". -- 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:30:14 UTC