This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13378 - 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.
Summary: Spec used to say "When a Document object is created, the document's character...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-27 00:02 UTC by contributor
Modified: 2011-09-27 19:12 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2011-07-27 00:02:16 UTC 
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
Comment 1 Michael[tm] Smith 2011-08-04 05:02:43 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-10 01:47:11 UTC 
Ms2ger, Anne: Do you recall anything about this difference?
Comment 3 Ms2ger 2011-08-10 11:07:04 UTC 
This was all Anne's doing. Encodings give me a headache.
Comment 4 Anne 2011-08-13 11:20:06 UTC 
I tested with createHTMLDocument and createDocument I believe and checked what the attributes returned in a couple of browsers.
Comment 5 Ian 'Hixie' Hickson 2011-08-31 23:29:52 UTC 
I wonder why I originally had UTF-16.
Comment 6 Ian 'Hixie' Hickson 2011-09-27 19:12:54 UTC 
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.