New issue
Advanced search Search tips

Issue 707231 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

chrome.downloads.download works incorrect

Reported by cas...@gmail.com, Mar 31 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. create an extension
2. file the following code in the background.js
3. chrome.downloads.download({url: link}, function(Id) {});

What is the expected behavior?
this function will download the page pointed by url and save into the save folder as chrome download.

What went wrong?
It works fine if the webpage only contains English or some other Western characters. But if the page contains Easter characters like Japanese, Chinese, Korean and so on, all these characters will be messy. It should be the character set problem.

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

Would be better to add one parameter to indicate the character set, or just follow the original page's character set.
 
Cc: pbomm...@chromium.org
Components: -Blink UI>Browser>Downloads
Labels: M-57
 casmyu@ if possible can you please provide the test extension for faster bisection please. 

Comment 2 by cas...@gmail.com, Mar 31 2017

pbomm... I find out the root cause now. Because my OS is English, and the default chrome text encoding follows the system environment. Btw, the text encoding is not allowed to change by users for the latest version of Chrome. The web page contains Chinese are encoded with GB 2312, which is different with my default text encoding. I tried to open the same webpage with Safari and changed text encoding to GB2312, and everything is fine.
Please close this ticket now. It's my fault, not a bug. 
SORRY!     
Status: WontFix (was: Unconfirmed)
Thank you casmyu@, based on comment#3 I am marking the bug as wontfix.

Sign in to add a comment