15900 2012-02-05 11:54:27 +0000 There is no use case for accept-charset to take multiple values. I think we should restrict it to a single value. 2012-08-23 17:26:45 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#attr-form-accept-charset P3 normal --- 1 contributor dave.null annevk eoconnor mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 63717 0 contributor 2012-02-05 11:54:27 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html Multipage: http://www.whatwg.org/C#attr-form-accept-charset Complete: http://www.whatwg.org/c#attr-form-accept-charset Comment: There is no use case for accept-charset to take multiple values. I think we should restrict it to a single value. Posted from: 82.161.179.17 by annevk@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.2; U; en) Presto/2.10.229 Version/11.60 63718 1 annevk 2012-02-05 11:57:29 +0000 (User agents will still have to handle multiple values. I suppose accept-charset="bogus big5 bogus2" works as using big5...) 70285 2 contributor 2012-07-18 07:16:01 +0000 This bug was cloned to create bug 17910 as part of operation convergence. 72617 3 eoconnor 2012-08-23 17:26:45 +0000 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: Additional Information Needed Change Description: No change. Rationale: If UAs have to support it, why not allow it?