Issue metadata
Sign in to add a comment
|
Chrome fails to display a local file with \u202a character in the file name
Reported by
xmillsa@tutanota.com,
Sep 17
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. Download test-case.zip 2. Extract it 3. Drag the extracted file into chrome What is the expected behavior? Display file content What went wrong? Your file was not found It may have been moved or deleted. ERR_FILE_NOT_FOUND Did this work before? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: 6.3 Flash Version: / The problem appears on Windows and Linux systems. Related: bug 792498 As said in the linked issue: "If you feel this issue should still be addressed, feel free to file a new issue.", so I'm filing a new issue, since I belivee the fix is probably not too hard to implement
,
Sep 18
(May deal with URL canonicalization)
,
Sep 18
The problem is that Chrome doesn't unescape URI file name. Debugging it with Windows Procmon reveals that Chrome is literally searching for "%E2%80%AA" instead of "". To prove it, create a file with name "%E2%80%AA" in the same directory. Let the content of that file be "Wrong file". Then open "" (original file) in Chrome and it will display "Wrong file".
,
Sep 18
Broken in Chrome 35: r254091 / 2cd905494ba700a8e2097d614ed39ad36d1519f2 Fixed in Chrome 69: r565176 / ee5e87f4b955407e31ac6357a9b164a9558fcfef Reporter, try updating your Chrome 67 to the current stable version, which is 69.
,
Sep 18
As mentioned, this seems fixed in M69. Reporter, please file a new bug if you are still seeing this on the latest version. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 18