On 2011-03-02 02:31, Tatham Oddie wrote:
Glenn,
That's an XP path you've provided.
On Vista or 7 it'd be:
C:\Users\tatham.oddie\AppData\Local\Google\Chrome\User
Data\Default\Storage
Microsoft explicitly did work in Vista to reduce the lengths of those base
paths.
Now, the Google
I'd like some clarification on the intent of the FileSystem API:
requestFileSystem permanent, getDirectory and getFile.
Are they intended to directly pass through to the host operating system,
or are they just programming constructs?
They're not particularly easy to use, compared to the
On Mon, 28 Feb 2011, Charles Pritchard wrote:
I'd like some clarification on the intent of the FileSystem API:
requestFileSystem permanent, getDirectory and getFile.
Are they intended to directly pass through to the host operating system, or
are they just programming constructs?
They're
On Mon, Feb 28, 2011 at 2:54 PM, Charles Pritchard ch...@jumis.com wrote:
I'd like some clarification on the intent of the FileSystem API:
requestFileSystem permanent, getDirectory and getFile.
The FileSystem API has several goals. Some of them are targeted by
the current spec, and some have
On Mon, Feb 28, 2011 at 7:10 PM, Eric Uhrhane er...@google.com wrote:
Our current implementation on Windows uses the standard API calls that
limit paths to 256 characters long. If your profile directory is
deeply nested [e.g. because you have a really long username], code
Worse, the profile
