13378 2011-07-27 00:02:16 +0000 Spec used to say "When a Document object is created, the document's character encoding must be initialized to UTF-16.", but DOM Core changes that to UTF-8. Should investigate. 2011-09-27 19:12:54 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#resource-metadata-management P3 normal --- 1 contributor ian annevk bzbarsky ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51518 0 contributor 2011-07-27 00:02:16 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Multipage: http://www.whatwg.org/C#resource-metadata-management Complete: http://www.whatwg.org/c#resource-metadata-management Comment: Spec used to say "When a Document object is created, the document's character encoding must be initialized to UTF-16.", but DOM Core changes that to UTF-8. Should investigate. Posted from: 216.239.45.4 by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.825.0 Safari/535.1 52570 1 mike 2011-08-04 05:02:43 +0000 mass-moved component to LC1 54541 2 ian 2011-08-10 01:47:11 +0000 Ms2ger, Anne: Do you recall anything about this difference? 54592 3 Ms2ger 2011-08-10 11:07:04 +0000 This was all Anne's doing. Encodings give me a headache. 54887 4 annevk 2011-08-13 11:20:06 +0000 I tested with createHTMLDocument and createDocument I believe and checked what the attributes returned in a couple of browsers. 56124 5 ian 2011-08-31 23:29:52 +0000 I wonder why I originally had UTF-16. 57433 6 ian 2011-09-27 19:12:54 +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: oh well, i can't work it out. hopefully we'll find out.