Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

DeviceStorage and file names that are illegal on the underlying file-system

Skip to first unread message

Andrew Sutherland

Mar 5, 2015, 8:58:49 PM3/5/15
On we're encountering the problem where
DeviceStorage is refusing to save a filename with a double-quote
character to the VFAT-formatted sdcard. (This isn't surprising,
although it's surprising we went this far without encountering the
problem! Note that I can happily download and save the file on
b2g-desktop on linux because of the awesome power of ext4.)

Prior-spec art seems to be which does specifying
that a normalization step should be performed on the name. (It says
replace all "/" characters with ":" characters. Since ":" is also
illegal on VFAT, we probably don't want that exactly.) The other file
APIs that I thought existed appear to have all been retracted.

Although it is quite feasible for the Gaia email app to perform a
filename normalization to VFAT, I thought it would be worth discussing
whether it would be advisable for DeviceStorage to automatically
normalize the filename to something legal. I believe callers have
already voided their warranty if they fail to look at the they get back from addNamed and use that, so this
could work for existing consumers even.

Arguments in favor of having DeviceStorage do it would be:
- We might not be using VFAT in all cases. Other file-systems could
have different rules. (Maybe HFS+ is crazy?)
- It's unlikely all callers will think to test with filenames that are
illegal on VFAT, so not doing it in DeviceStorage is just helping
developers shoot themselves and their/our users in their feet.
- There can be other complications like MAX_PATH on Windows that might
require name truncation, especially since non-chrome JS code has no
chance of knowing the mount points/etc. in play.
- Non-security unicode issues where non-ASCII things don't work.
- Complicated hypothetical security/attack unicode issues like

In the event there are emerging standards that DeviceStorage will
converge to/etc., I think we should just do what they're doing and I'm
happy for people to point me at them.


Ehsan Akhgari

Mar 6, 2015, 8:54:44 AM3/6/15
to Andrew Sutherland,, Dave Hylands,
It seems that the new FileSystem spec also points to the File
Constructor spec for file name normalization. CCing Arun.

I think it's pretty hard to come up with a future proof normalization
scheme that works across all filesystems, and it should probably be up
to the implementation to protect against some of these unacceptable
characters. The interesting thing about DeviceStorage is that these
files are also expected to be visible to humans, so we should think
about whether saving the file under a different name than the one
provided to the API makes sense. I personally don't think that's a big
> _______________________________________________
> dev-webapi mailing list

Jonas Sicking

Mar 6, 2015, 3:05:43 PM3/6/15
to Ehsan Akhgari, Dave Hylands,, Andrew Sutherland,
I don't think any W3C spec is going to address our needs here. W3C has
explicitly stayed away from allowing writes to the user's filesystem
for various security reasons, and so won't need to tackle this issue.

I think the question here is how we want our DeviceStorage API to
behave. I see two possible options:

1. Silently change the filename to something which can be written to
the filesystem.
2. Fire an error event (which possibly includes a suggested fixed-up name).

I don't really have any strong opinion. Doing 1 definitely runs the
risk of having application databases and data structures get
out-of-sync with what's actually on the filesystem.

So I think 2 would get my vote.

/ Jonas

Arun Ranganathan

Mar 7, 2015, 10:18:47 PM3/7/15
to Jonas Sicking, Dave Hylands,, Ehsan Akhgari, Andrew Sutherland,
So when File API (best accessed here:
and not as "TR") disallowed "/" it was just reifying existing behavior.
That is, conversion of "/" to ":".

But the VFAT issue is clearly a problem that we didn't anticipate :(

I'm happy to modify this, but some suggestions would be good. In general,
we take UTF16 and try and disallow reserved chars. Maybe we should have an
expanded list of reserved chars that we disallow. Not 100% sure we can be
normative about this in the spec., as Jonas says.

Ehsan Akhgari

Mar 16, 2015, 5:02:02 PM3/16/15
to Jonas Sicking, Dave Hylands,, Andrew Sutherland,
Dropbox seems to have this list <> which we
can probably use. Credits for finding it go to Arun!
0 new messages