- From: Arun Ranganathan <arun@mozilla.com>
- Date: Tue, 3 Sep 2013 10:03:06 -0400
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WebApps WG <public-webapps@w3.org>
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? 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. On Aug 29, 2013, at 10:48 AM, Anne van Kesteren wrote: > As currently specified File's name property seems to be a code unit > sequence. In zip archives the resource's path is a byte sequence. I > don't really know what popular file systems do. Given that a File has > to be transmitted over the wire now and then, including it's name > property value, a code unit sequence seems like the wrong type. It > would at least lead to information loss which I'm not sure is > acceptable if we can prevent it (or at least make it more obvious that > it is going on, by doing a transformation early on). > > We may also want to restrict "\" and "/" to leave room for using these > objects in path-based contexts later. > > > -- > http://annevankesteren.nl/ >
Received on Tuesday, 3 September 2013 14:03:54 UTC