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 17910 - 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: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:15 UTC by contributor
Modified: 2012-10-22 21:49 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:15:58 UTC 
This was was cloned from bug 15900 as part of operation convergence.
Originally filed: 2012-02-05 11:54:00 +0000

================================================================================
 #0   contributor@whatwg.org                          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
================================================================================
 #1   Anne                                            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...)
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-08-09 15:49:30 UTC 
If UAs have to support it, why not allow it?
Comment 2 Anne 2012-08-27 06:26:31 UTC 
If we only allow legal encoding names in there, there is no point in using more than one value, because UAs will be required to support the same set of encodings (in due course). So specifying two legal values would be pointless and may in fact be confusing as to what will happen.
Comment 3 Ian 'Hixie' Hickson 2012-08-31 23:52:39 UTC 
How's that going? (Requiring a specific set of encodings.) Do we have agreement from vendors to remove support for unlisted encodings?

I'm not sure really what harm this causes. I mean, I'm not saying that I would design it this way intentionally, but since it's there... are there no actively-maintained pages with multiple values? (If there are, surely this will cause those authors to waste more time removing stuff for no reason.)