- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 3 Sep 2013 16:17:02 +0100
- To: Arun Ranganathan <arun@mozilla.com>
- Cc: WebApps WG <public-webapps@w3.org>
On Tue, Sep 3, 2013 at 3:03 PM, Arun Ranganathan <arun@mozilla.com> wrote: > Well, https://www.w3.org/Bugs/Public/show_bug.cgi?id=23138 is to make the 'type' attribute a ByteString. Is that your request here for the name attribute as well? I don't think you want those conversion semantics for name. I do think we want the value space for names across different systems to be equivalent, which if we support zip basically means bytes. This could mean accepting DOMString and then doing the conversion yourself through utf-8. However, it's not very clear to me how to do the conversion back in a way that minimizes information loss and works everywhere compatibly. For zip archives I ended up with rawPath (bytes) and path (bytes converted to a string using utf-8 and vice versa). Maybe we should use that model here too? > It wouldn't be wise to restrict '/' or '\' or try to delve too deep into platform land BUT the FileSystem API introduces directory syntax which might make being lax a fly in the ointment for later. Right. Zip archives also have paths and it would be annoying if we ran into problems there. -- http://annevankesteren.nl/
Received on Tuesday, 3 September 2013 15:17:33 UTC