- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 29 Aug 2013 16:14:28 +0100
- To: Glenn Maynard <glenn@zewt.org>
- Cc: Arun Ranganathan <arun@mozilla.com>, WebApps WG <public-webapps@w3.org>
On Thu, Aug 29, 2013 at 4:10 PM, Glenn Maynard <glenn@zewt.org> wrote: > I don't think it makes sense to expect filenames to round-trip through > File.name, especially for filenames with a broken or unknown encoding. > File.name should be a best-effort at converting the platform filename to > something that can be displayed to users or encoded and put in a > Content-Disposition header, not an identifier for finding the file later. File has a constructor. We should be clearer about platforms too I suppose. >> We may also want to restrict "\" and "/" to leave room for using these >> objects in path-based contexts later. > > Forward slash, but not backslash. That's a platform-specific restriction. > If we go down the route of limiting filenames which don't work on one or > another system, the list of restrictions becomes very long. If path > separators are exposed on the web, they should always be forward-slashes. Given that the URL parser treats them identically, we should treat them identically everywhere else too. -- http://annevankesteren.nl/
Received on Thursday, 29 August 2013 15:14:56 UTC