Re: [FileAPI] Don't use [EnsureUTF16] (gone from Web IDL) (#9)

>>How would you then transmit that filename? Everything part of File needs to be serialized. DOMString cannot be serialized.

Well, WebIDL does include an algorithm for converting a DOMString to a sequence of Unicode scalar values and is part of the DOMString definition, so we *can* serialize them after doing something like that. 

But if this bug is to replace [EnsureUTF16] with USVString as a type instead of DOMString, then maybe that's ok especially since it's in Gecko. 

Separately, the current check for illegal chars in fileName may be inadequate. Right now, we only replace "/" with ":" which may be wrong on some OS's. I wonder if we should do a more exhaustive check, sort of like this (scroll down): https://www.dropbox.com/help/145 and in general include more for fileName's definition.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/9#issuecomment-126730119