New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 788429 link

Starred by 2 users
Status: Duplicate
Merged: issue 785209
Owner:
jinsuk...@chromium.org
Closed: Nov 2017
Cc:
█ krajshree@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Compat



Sign in to add a comment

Automatic page encoding detection does not work sometimes

Reported by pub...@buzden.ru, Nov 24 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Example URL:
http://jaffar.cs.msu.ru/mash/os/2016%202017/

Steps to reproduce the problem:
1. Open given URL which contains cyrillic symbols
2. Voila!

What is the expected behavior?
Correct page encoding autodetection was expected due to lack of manual encoding setting facility.

What went wrong?
Encoding of a cyrillic page with some unusual encoding was not detected correctly leading to wrong page content.

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? N/A

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 
Flash Version: 

If you save this page and open the saved copy, encoding detection works correctly. Maybe, the reason is in the shadow root of the original page?
chrome-encoding-bug.png
79.1 KB View Download

Comment 1 by krajshree@chromium.org, Nov 27 2017

Cc: krajshree@chromium.org
Components: Blink>TextEncoding
Labels: Needs-Feedback Triaged-ET Needs-Triage-M62
public@ - Thanks for filing the issue...!!

Issue doesn't seem to be chrome-specific. The webpage at URL: http://jaffar.cs.msu.ru/mash/os/2016%202017/ yields same results as chrome as in the attached screenshot at comment #0.

Could you please check the behaviour of other browsers also.

Thanks...!!

Comment 2 by pub...@buzden.ru, Nov 27 2017 

Bug of wrong autodetection seems to be not chrome-specific, yes. I've checked at least Firefox.

But chrome is the only browser (which, at least, I know) that does not give an ability to set encoding manually. Thus, chrome-specific thing is that users do not even have an ability to see this page normally. Probably, plugins that compensate turned off ability of manual setting exist, but still, chrome's encoding autodetection was praised so much when manual setting gone away, so it must uphold the reputation, don't you think so? ;-)
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 27 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by jsb...@chromium.org, Nov 27 2017

Owner: jinsuk...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by jinsuk...@chromium.org, Nov 27 2017

Mergedinto: 785209
Status: Duplicate (was: Assigned)
Please consider using a Chrome extension https://chrome.google.com/webstore/detail/set-character-encoding/bpojelgakakmcfmjfilgdlmhefphglae
►

Sign in to add a comment