The standard is so clear about the issue that we can't do anything about it whether we like it or not. The HTTP header Content-Type has a higher precedence than the meat tag. You'd better contact the site admin to get rid of 'charset=xxxx' in the HTTP Content-Type header. ONLY when 'charset=xxxx' is absent, 'charset' in the meta tag comes into the scene.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.