New issue
Advanced search Search tips

Issue 904225 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Compat


Show other hotlists

Hotlists containing this issue:
Test


Sign in to add a comment

Encoding is not detected correctly

Reported by abhamora...@gmail.com, Nov 11

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Example URL:
http://faculty.chicagobooth.edu/ruey.tsay/teaching/fts2/

Steps to reproduce the problem:
1. Copy the URL in URL bar.
2. Press Enter.
3. 

What is the expected behavior?
The webpage is supposed to run on encoding Unicode (UTF-16LE). Which is not rightly detected. The updated version of chrome doesn't have encoding option where we can choose the right code.

What went wrong?
The text on the webpage is garbled like a code language. The webpage is supposed to run on encoding Unicode (UTF-16LE). Which is not rightly detected. The updated version of chrome doesn't have encoding option where we can choose the right code.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.77  Channel: n/a
OS Version: 10.0
Flash Version:
 
Labels: Needs-Triage-M70
All versions of Chrome since at least 12 can't detect UTF-16LE on that URL.
It might make sense to detect the simplest case - ASCII in UTF-16LE - as it's super trivial.
On the other hand, that is the server's fault: it's not configured to set the encoding header in its responses.

Until this is resolved you can use an extension:
https://chrome.google.com/webstore/search/encoding?_category=extensions
It worked. Thank you very much.
Cc: phanindra.mandapaka@chromium.org
Components: UI>Browser
Labels: Triaged-ET Target-72 M-72 FoundIn-71 FoundIn-70 FoundIn-72 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
As per comment #0, able to reproduce the issue on reported chrome version 70.0.3538.77 also on latest chrome 72.0.3608.0 using Mac 10.14.0, Ubuntu 17.10 and Windows 10.  
 
Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged.

Thanks! 

Sign in to add a comment