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 12152 - Charset attribute is (in HTML 4) supposed to inform the browser beforehand about the encoding (before making an HTTP request), and it may also be useful if the resource is not transferred via HTTP or it is sent without suitable Content-Type header. The cu
Summary: Charset attribute is (in HTML 4) supposed to inform the browser beforehand ab...
Status: RESOLVED NEEDSINFO
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-02-22 14:45 UTC by contributor
Modified: 2011-08-04 05:14 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-02-22 14:45:07 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#non-conforming-features

Comment:
Charset attribute is (in HTML 4) supposed to inform the browser beforehand
about the encoding (before making an HTTP request), and it may also be useful
if the resource is not transferred via HTTP or it is sent without suitable
Content-Type header. The current formulation about it seems to be based on
partial misunderstanding. I think the attribute should be preserved in HTML5.

Posted from: 88.114.29.18
Comment 1 Ian 'Hixie' Hickson 2011-05-04 23:54:52 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: Did Not Understand Request
Change Description: no spec change
Rationale: Do people actually use it? Do browsers actually implement it?
Comment 2 Michael[tm] Smith 2011-08-04 05:14:22 UTC 
mass-move component to LC1