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

Issue 736814 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
kouhei@chromium.org
█ sandeepkumars@chromium.org
jinsuk...@chromium.org
js...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt displays with wrong encoding

Reported by jrnieder@gmail.com, Jun 26 2017 
Chrome Version       : 59.0.3071.109 (Official Build) (64-bit)
URLs (if applicable) : https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt

What steps will reproduce the problem?
(1) Visit https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt
(2) Try to read.

What is the expected result?
Non-breaking spaces show as non-breaking spaces.

What happens instead?
Non-breaking spaces show as A with a macron on top:
Appendix A. Upgrading checklist

Please provide any additional information below. Attach a screenshot if
possible.
This page is UTF-8 encoded, but Chrome appears to be misinterpreting it as an 8bit encoding instead.

Developer tools show

 Content-Type:text/plain

which means it should auto-detect.

Comment 1 by sandeepkumars@chromium.org, Jun 27 2017

Labels: Needs-Feedback
Tested this issue using reported version #59.0.3071.109 on Mac 10.12.5 and was unable to reproduce the issue.

@jrnieder: Could you please add the OS labels on which OS you're facing the issue? and if possible please attach a expected screenshot of the exact issue. That would help us in further triaging of the issue.

Please find the below screenshot.

Thanks!!
Screen Shot 2017-06-27 at 4.55.16 PM.png
194 KB View Download

Comment 2 by jrnieder@gmail.com, Jun 27 2017 

I don't have the ability to set labels.  I'm on Ubuntu trusty.
Project Member

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

Cc: sandeepkumars@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@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 jrnieder@gmail.com, Jun 27 2017 

Google Chrome	59.0.3071.109 (Official Build) (64-bit)
Revision	8d31b54270a793a0f98e76579c8fd0405bbd6ac6-refs/branch-heads/3071@{#805}
OS	Linux
JavaScript	V8 5.9.211.38
Flash	26.0.0.131 /usr/local/google/home/jrn/.config/google-chrome/PepperFlash/26.0.0.131/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.109 Safari/537.36
Command Line	/usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end
upgrading-checklist.png
149 KB View Download

Comment 5 by eroman@chromium.org, Jun 29 2017

Components: Blink>Loader
I can reproduce. I don't recall where we infer encoding in this case (net stack or blink loading stack). Tentatively labeling Blink>Loader.

Comment 6 by toyoshim@chromium.org, Jul 4 2017

Cc: kouhei@chromium.org
Labels: OS-Linux
Status: Untriaged (was: Unconfirmed)
I can repro on Linux, but can not on CrOS.

cc: kouhei who may know where is the encoding detection for plain texts.

Comment 7 by yhirano@chromium.org, Jul 11 2017

Cc: jinsuk...@chromium.org js...@chromium.org
Components: -Blink>Loader Blink>TextEncoding
Firefox (on Linux and Mac) and Safari show the same behavior.

Comment 8 by jsb...@chromium.org, Jul 12 2017

Status: WontFix (was: Untriaged)
Working as intended.

File doesn't have a BOM and it isn't being served with an encoding in the Content-Type header. We intentionally don't try and guess UTF-8 so as to not break compat with other browsers.

See issue 691985

Comment 9 by jrn@google.com, Jul 12 2017 

Weird, thank you. Does this mean CrOS has a bug in the opposite direction?

I'll poke the server admin to get their Content-Type set right.
►

Sign in to add a comment