9141 2010-02-24 21:45:08 +0000 10.2.2.2: overriding explicitly declared encodings is a bad idea maybe make this only for when both HTTP and HTML didn't specify the encoding 2010-10-04 14:45:31 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#character-encodings-0 P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32631 0 contributor 2010-02-24 21:45:08 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#character-encodings-0 Comment: 10.2.2.2: overriding explicitly declared encodings is a bad idea maybe make this only for when both HTTP and HTML didn't specify the encoding Posted from: 64.139.38.226 34064 1 ian 2010-03-29 05:53:31 +0000 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: Assuming you mean the "misinterpreted for compatibility" bit, we don't have any choice about this. It's how the Web works in practice.