7895 2009-10-12 08:49:30 +0000 In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding 2010-10-04 14:46:26 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#documentEncoding NE P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28258 0 contributor 2009-10-12 08:49:30 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#documentEncoding Comment: In step 6, it should be allowed (and clear that it is allowed) for UAs to use additional data such as the site TLD to guess the correct encoding Posted from: 88.131.66.80 28653 1 ian 2009-10-21 05:43:04 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 28654 2 contributor 2009-10-21 05:43:58 +0000 Checked in as WHATWG revision r4230. Check-in comment: Allow UAs to use the URL to sniff encoding. http://html5.org/tools/web-apps-tracker?from=4229&to=4230