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 15900 - There is no use case for accept-charset to take multiple values. I think we should restrict it to a single value.
Summary: There is no use case for accept-charset to take multiple values. I think we s...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-05 11:54 UTC by contributor
Modified: 2012-08-23 17:26 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2012-02-05 11:54:27 UTC 
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
Comment 1 Anne 2012-02-05 11:57:29 UTC 
(User agents will still have to handle multiple values. I suppose accept-charset="bogus big5 bogus2" works as using big5...)
Comment 2 contributor 2012-07-18 07:16:01 UTC 
This bug was cloned to create bug 17910 as part of operation convergence.
Comment 3 Edward O'Connor 2012-08-23 17:26:45 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: Additional Information Needed
Change Description: No change.
Rationale: If UAs have to support it, why not allow it?