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 22010 - Carry over (or add) a charset parameter where applicable
Summary: Carry over (or add) a charset parameter where applicable
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: MIME (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Gordon P. Hemsley
QA Contact: sideshowbarker+mimespec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 21307
  Show dependency tree / graph
 
Reported: 2013-05-11 14:17 UTC by Gordon P. Hemsley
Modified: 2019-03-30 19:51 UTC (History)
2 users (show)

See Also:

Attachments

Description Gordon P. Hemsley 2013-05-11 14:17:56 UTC 
For text (or text-like) MIME types, the character encoding is crucially important. Right now, the sniffing algorithm mostly just throws it away, even when the information is known.

The spec should better handle the cases where a charset parameter is present in the supplied MIME type and when the charset parameter can be set according to the BOM.

See also: bug 22009.
Comment 1 Anne 2019-03-30 19:51:18 UTC 
As I mentioned elsewhere, I'm not convinced we should change much to the status quo.