Chrome fails to display a local file
Reported by
hakerh403@gmail.com,
Dec 6 2017
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Steps to reproduce the problem:
1. Create a file with name '\u202a' (without quotes)
2. In step 1 the file name is only 1 char long (it is literal unicode character with charCode 0x202A), not 6 chars
3. Drag the file into Chrome
What is the expected behavior?
The content of the file should be displayed.
What went wrong?
The following message is displayed
Your file was not found
It may have been moved or deleted.
ERR_FILE_NOT_FOUND
Chrome parses the file name as "%E2%80%AA". It is indeed correct unicode representation, but for some reason it fails to display the content of the file.
The issue is not seen in other browsers and it works properly even in Firefox.
Did this work before? N/A
Chrome version: 62.0.3202.75 Channel: stable
OS Version: 6.3
Flash Version: /
,
Dec 7 2017
Here is the file (not the archive itself, the actual file is in the archive).
,
Dec 7 2017
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
,
Dec 8 2017
Able to reproduce this issue on reported version 62.0.3202.94 and on latest canary 65.0.3258.0 using Windows 10 and Ubuntu 14.04. Unable to check this issue on Mac as we are seeing error on opening attached file. This issue is seen from M50[50.0.2661.0] Hence considering this issue as Non-Regression and marking as Untriaged. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Dec 7 2017Labels: Triaged-ET Needs-Feedback Needs-Triage-M62