- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Feb 2011 14:45:08 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12152 Summary: 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 Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#non -conforming-features OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org 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 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 22 February 2011 14:45:11 UTC