Chrome cannot select the correct character encoding
Reported by
go2super...@gmail.com,
Mar 27 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Example URL: http://www.flashget.com/tw/addons.htm Steps to reproduce the problem: 1. Just visit the URL and you can see the problem. What is the expected behavior? What went wrong? When you visit some Traditional-Chinese page, Chrome cannot select the correct character encoding (it's should be Big5 or Unicode, not GB2312). So those pages looks weird. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 56.0.2924.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0
,
Apr 3 2017
Able to reproduce the issue on windows 7, Ubuntu 14.04 and Mac 10.12.3 using chrome version 57.0.2987.133 and canary 59.0.3060.1. This is non regression issue as the issue seen from M30 old builds. Marking it as Untriaged to get more inputs form Dev. Thanks,
,
Apr 3 2017
,
Apr 4 2017
,
Apr 4 2017
File is being served with a header: Content-Type: text/html; charset=utf8 Document also contains: <meta http-equiv="Content-Type" content="text/html; charset=big5"> After loading, document.charset returns: "UTF-8". Appearance is the same in both Firefox and Chrome (both are interpreting as UTF-8)
,
Apr 4 2017
I think this is working as expected - encoding info in HTTP header takes precedence over the one in the document meta tag. Please use a chrome extension (one mentioned here https://bugs.chromium.org/p/chromium/issues/detail?id=597488#c70) to switch encoding manually. Let me mark it as WontFix. Feel free to reopen it if there's other things to take into account.
,
Apr 4 2017
Same behavior in Safari. Per https://html.spec.whatwg.org/multipage/syntax.html#determining-the-character-encoding "3. If the transport layer specifies a character encoding, and it is supported, return that encoding with the confidence certain, and abort these steps." Also note: https://www.w3.org/International/questions/qa-html-encoding-declarations "The HTTP header information has the highest priority when it conflicts with in-document declarations other than the byte-order mark." Working as intended. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ligim...@chromium.org
, Mar 31 2017