17910 2012-07-18 07:15:58 +0000 There is no use case for accept-charset to take multiple values. I think we should restrict it to a single value. 2012-10-22 21:49:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#attr-form-accept-charset P3 normal Unsorted 1 contributor ian annevk ian mike contributor oldest_to_newest 70284 0 contributor 2012-07-18 07:15:58 +0000 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...) ================================================================================ 71969 1 ian 2012-08-09 15:49:30 +0000 If UAs have to support it, why not allow it? 72804 2 annevk 2012-08-27 06:26:31 +0000 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. 73128 3 ian 2012-08-31 23:52:39 +0000 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.)