Re: [w3c/FileAPI] Specify how filenames from the OS map to File's `name` property (#161)

It's fine if things are left implementation-defined, but maybe it'd be worth it to add a note about expected behavior:

> Although the conversion from a native filename into a string is implementation-defined, it is expected to be a straightforward mapping. In particular, if the system's filenames are represented as sequences of [code units](https://infra.spec.whatwg.org/#code-unit), the resulting strings should be identical; and if they are represented as [byte sequences](https://infra.spec.whatwg.org/#byte-sequence), they should be decoded from the OS's default encoding with the "`replacement`" [error mode](https://encoding.spec.whatwg.org/#error-mode).

I think at the very least the spec should make clear that the empty string fallback should be for OS errors when reading the filename – decoding the filename should always succeed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/161#issuecomment-791471515