Re: [whatwg] Using requestFileSystem to setup mounts

Hi, what about window.MOUNT_ONCE - mount only for current session - would open select folder dialog window.MOUNT_ALWAYS - mount for all time (or to be more precise for the time of life time of IndexDB, cookies, etc). - user have to give explicit permission for this and only after this permissio

Re: [whatwg] Using requestFileSystem to setup mounts

On Mon, Nov 28, 2011 at 9:18 AM, Kinuko Yasuda wrote: > On Wed, Nov 23, 2011 at 1:58 AM, Glenn Maynard wrote: > >> This would lead to interop problems if it's not consistent, though. For >> example, if my application creates ZIP files, and the user drags two files >> into the root directory of

Re: [whatwg] Using requestFileSystem to setup mounts

(Sorry for my slow response) On Wed, Nov 23, 2011 at 1:58 AM, Glenn Maynard wrote: > On Tue, Nov 22, 2011 at 6:06 AM, Kinuko Yasuda wrote: > >> Putting aside the API discussion, actually I like the idea having one >> shared >> isolated filesystem that contains multiple directories/files being >

Re: [whatwg] Using requestFileSystem to setup mounts

On Tue, Nov 22, 2011 at 6:06 AM, Kinuko Yasuda wrote: > Putting aside the API discussion, actually I like the idea having one > shared > isolated filesystem that contains multiple directories/files being dropped > in, > as in that way both the UA and script can easily distinguish the set of > dr

Re: [whatwg] Using requestFileSystem to setup mounts

On Tue, Nov 22, 2011 at 7:30 AM, Glenn Maynard wrote: > On Mon, Nov 21, 2011 at 4:33 PM, Charles Pritchard wrote: >> >> Multiple directories still have a shared file system root. Their relative >> paths are exposed in webkitdirectory files already. >> The benefit is neutered .files object while m

Re: [whatwg] Using requestFileSystem to setup mounts

On Mon, Nov 21, 2011 at 4:33 PM, Charles Pritchard wrote: > ** > Multiple directories still have a shared file system root. Their relative > paths are exposed in webkitdirectory files already. > The benefit is neutered .files object while maintaining compatibility with > existing code bases. > I

Re: [whatwg] Using requestFileSystem to setup mounts

On 11/21/11 8:45 AM, Glenn Maynard wrote: On Mon, Nov 21, 2011 at 9:10 AM, Kinuko Yasuda > wrote: On Sun, Nov 20, 2011 at 5:54 AM, Charles Pritchard mailto:ch...@jumis.com>> wrote: > input.ondrop = function(e) { > window.requestFileSystem(e.dataTransf

Re: [whatwg] Using requestFileSystem to setup mounts

On 11/21/11 6:10 AM, Kinuko Yasuda wrote: Hi, thanks for your comment! On Sun, Nov 20, 2011 at 5:54 AM, Charles Pritchard wrote: // Proposal, using DataTransfer with rFS: input.ondrop = function(e) { window.requestFileSystem(e.dataTransfer, 0, cb); } There's some slight room for delaying

Re: [whatwg] Using requestFileSystem to setup mounts

I wish people wouldn't randomly split threads. This isn't a different conversation. On Mon, Nov 21, 2011 at 9:10 AM, Kinuko Yasuda wrote: > On Sun, Nov 20, 2011 at 5:54 AM, Charles Pritchard > wrote: > > input.ondrop = function(e) { > > window.requestFileSystem(e.dataTransfer, 0, cb); > > } >

Re: [whatwg] Using requestFileSystem to setup mounts

Hi, thanks for your comment! On Sun, Nov 20, 2011 at 5:54 AM, Charles Pritchard wrote: > Kinuko Yasuda, I saw your post to whatwg regarding drag-and-drop directory > mounts. > > I'm sure you've seen the various concerns people have with the proposal.. > Like others, I'm also concerned about the s

[whatwg] Using requestFileSystem to setup mounts

Kinuko Yasuda, I saw your post to whatwg regarding drag-and-drop directory mounts. I'm sure you've seen the various concerns people have with the proposal.. Like others, I'm also concerned about the security implications of traversing a directory and sealing the action upon drop, or otherwise s