NEED ENCODING MENU BACK
Reported by
zhifangy...@gmail.com,
Mar 23 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. NEED ENCODING MENU BACK 2. NEED ENCODING MENU BACK 3. NEED ENCODING MENU BACK What is the expected behavior? What went wrong? NEED ENCODING MENU BACK Did this work before? N/A Chrome version: 57.0.2987.110 Channel: stable OS Version: OS X 10.12.3 Flash Version:
,
Mar 24 2017
Considering this as feature request, marking it as untriaged As per " Issue 597488 ", this change was intentional.
,
Mar 29 2017
Hi zhifangyizhiyang@, could you give any sample URL or file which Chrome does not auto-detect the encoding for correctly? CC'ing jinsukkim@ as you seem to know the most about this. There does seem to be a sample file included in Issue 703006 that is not auto-detected for me in Chrome Canary 59.0.3054.0 (it does work in stable 56.0.2924.87), but I thought I should leave judgement to you about whether there is scope to improve the auto-detection or just recommend installing an extension. Thanks very much!
,
Mar 29 2017
Oops, this should be UI>Internationalisation to be consistent with Issue 597488 .
,
Mar 29 2017
see attachment. auto detecting does not work for that file. It should be utf-8. If I add "<meta charset='utf-8'>" in the file, it will display correctly. My Chrome version " 57.0.2987.110 (64-bit)" on Macbook macOS Sierra 10.12.3
,
Mar 29 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by zhifangy...@gmail.com
, Mar 23 2017