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 13138 - DOM Core: set concept-document-media-type
Summary: DOM Core: set concept-document-media-type
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 11:44 UTC by Anne
Modified: 2012-02-03 13:38 UTC (History)
6 users (show)

See Also:


Attachments

Description Anne 2011-07-05 11:44:27 UTC
When a Document object is created its associated media type needs to be set so document.contentType correctly returns "image/jpeg" when loading JPEG images.

http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-document-contenttype
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-document-media-type
Comment 1 Michael[tm] Smith 2011-08-04 05:35:47 UTC
mass-move component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-19 04:15:56 UTC
Can we change "media type" to a term that doesn't conflict with either HTTP MIME types or CSS media types?

Maybe even "content type", since that's the name of the attribute?

Also, do we really need this feature?

Please reassign to me if you change the term.
Comment 3 contributor 2011-08-19 04:16:03 UTC
Checked in as WHATWG revision r6515.
Check-in comment: DOM Core compatibility (Document.contentType values)
http://html5.org/tools/web-apps-tracker?from=6514&to=6515
Comment 4 Anne 2011-12-19 13:02:13 UTC
Because I'm always over thinking naming I decided to take a long time to decide "content type" is fine.

https://bitbucket.org/ms2ger/dom-core/changeset/ae2a18547a16

The feature allows for distinguishing between the various types of formats that instantiate a Document when loaded in a browsing context. Slightly more useful than characterSet and introduced mostly because more browsers want to implement it.

By the way, I also renamed "character encoding" to "encoding" (concept-document-encoding).
Comment 5 Ian 'Hixie' Hickson 2012-01-13 23:11:07 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 6 Anne 2012-02-03 13:38:50 UTC
http://html5.org/r/6897