- From: <bugzilla@jessica.w3.org>
- Date: Sat, 10 Mar 2012 09:18:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16303
Julian Reschke <julian.reschke@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |julian.reschke@gmx.de
--- Comment #1 from Julian Reschke <julian.reschke@gmx.de> 2012-03-10 09:18:49 UTC ---
IMHO this is a good example of over-specification. Having multiple charset
parameters is invalid, specifying the wrong charset is a bug, and relying on
case in charset names is a bug. So this specifies behavior for a case of a
double client bug + a server bug at the same time.
As far as I can tell, no UA except FF has tried to implement this yet; and the
implementation in FF has required lots of hacks and layering violations
(essentially, the header field parser needs to preserve all kinds of state that
otherwise wouldn't be needed). Furthermore, it also doesn't do this for "all"
charset parameters.
My suggestion would be to drop that silly requirement, and jut clarify that if
you specify the charset although XHR will override it, you're on your own.
--
Configure bugmail: https://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 Saturday, 10 March 2012 09:18:52 UTC