[Webkit-unassigned] [Bug 81270] New: [Chromium] FileApi does not handle files with NFD encoded umlaut in file name

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=81270

           Summary: [Chromium] FileApi does not handle files with NFD
                    encoded umlaut in file name
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tbarzic at chromium.org
                CC: ericu at chromium.org


Files with NFD encoded characters (e.g. a umlaut encoded as a%CC%88) in name are not handled well in Chromium OS file manager. (see http://crosbug.com/ 26028)

When we do file system operations we use file's url as an argument. When the url gets created from the file name, it gets normalized to NFC encoding.
When the file name gets extracted from the url on Chromium side, it contains %C3%A4 (NFC encoding of a umlaut) instead of a%CC%88, and file operations fail because we cannot find the specified file path on the disk. (we search for foo0xc30xa4.foo instead of fooa0xcc0x88).

The file gets shown in the file manager, but it becomes useless (we cannot do anything with it).
Note that fileEntry object contains correctly encoded file name/path.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.