W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2012

[whatwg] FileList usage

From: Charles Pritchard <chuck@jumis.com>
Date: Fri, 02 Mar 2012 19:56:29 -0800
Message-ID: <4F51966D.1030301@jumis.com>
File and FileList are broken anyway. It was assumed, more or less, that 
underlying files would not change once added.
They can be deleted or altered. webkit has the webkitDirectory semantics 
on top of it.

My thinking is to eventually fix it via rFS:

Because rFS expects that kind of silliness to happen.

In the meantime, File objects are mutable in WebKit, though they 
shouldn't be, and they're misreported in Mozilla.
I spoke up about using FileList as a live structure, Glenn had this 

I wasn't able to get consensus about a File watcher API, which I'd 
really like to have, and is quite a normal request.

And that's the whole chunk of mess about File and FileList.

I just don't want to lose my live File in webkit without getting a 


On 2/29/2012 12:30 PM, Daniel Cheng wrote:
> FileList is supposed to be live, though it isn't today in WebKit.
> Daniel
> On Wed, Feb 29, 2012 at 12:14, Boris Zbarsky <bzbarsky at mit.edu 
> <mailto:bzbarsky at mit.edu>> wrote:
>     On 2/29/12 2:58 PM, Charles Pritchard wrote:
>             I'm pretty sure the live ones can't right?
>         If it's behind a method call, perhaps even a parent attribute,
>         there's opportunity to regenerate, long as there aren't too
>         many sites out there optimizing out the access call.
>     That a big "as long as".
>     It's demonstrably false for CSSRuleList and StyleSheetList.
>     I can't speak to FileList.
>     -Boris
Received on Friday, 2 March 2012 19:56:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC