This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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".
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: Accepted Change Description: see diff given below Rationale: Fine, fine, fine.
Checked in as WHATWG revision r5565. Check-in comment: List some of the differences, to make Julian happier. http://html5.org/tools/web-apps-tracker?from=5564&to=5565