This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24586 - Remove FileList
Summary: Remove FileList
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 23682
Blocks: 17125
  Show dependency tree / graph
 
Reported: 2014-02-08 00:20 UTC by Jonas Sicking (Not reading bugmail)
Modified: 2015-10-19 15:47 UTC (History)
3 users (show)

See Also:

Attachments

Description Jonas Sicking (Not reading bugmail) 2014-02-08 00:20:47 UTC 
Bug 23682 seems to be solving the issue of how to return a JS-array of Foo objects rather than having to introduce new FooList types.

This means that we can remove FileList.

This should be a backwards compatible change spec-wise. Some implementations supports the syntax myfilelist.item(5) which would be lost in this change. But given that no one has asked for the .item function to be brought back, hopefully this should be fine.
Comment 1 Jan Varga 2014-02-10 09:46:27 UTC 
So we don't have to fix IDB implementation to support it :)
Comment 2 Arun 2014-02-10 15:49:31 UTC 
OK, but what is the best strategy for feature requests?  For example, Bug 17125 calls for a .drop(itemNumber) method to be added. Without a custom interface, what can we extend or work with?
Comment 3 Jonas Sicking (Not reading bugmail) 2014-02-10 17:10:44 UTC 
That's the beauty. If we use the proposed solution in bug 23682 and use Arrays rather than FileList, then we leverage the existing feature set of Arrays. I.e. things like FileList.drop(whatever) isn't needed since Arrays already have that functionality.
Comment 4 Arun 2014-02-10 17:55:10 UTC 
(In reply to Jonas Sicking from comment #3)
> That's the beauty. If we use the proposed solution in bug 23682 and use
> Arrays rather than FileList, then we leverage the existing feature set of
> Arrays. I.e. things like FileList.drop(whatever) isn't needed since Arrays
> already have that functionality.

I guess in the case of something like FileList, all "new proposal" operations (like .drop(item)) will be list operations envisioned for an iterable type, which I guess Array gives us out of the box.

OK, I'm sold :)
Comment 5 Arun 2014-11-18 20:52:42 UTC 
We've marked this "at risk" but haven't removed it, owing to the other platform bits that need to happen.
Comment 6 Jonas Sicking (Not reading bugmail) 2014-11-18 21:06:26 UTC 
Once bug 23682 is fixed, we can probably just do |typedef FileList FrozenArray<File>;|. This way we don't have to depend on others to remove it from their spec.
Comment 7 Arun 2015-10-19 15:47:52 UTC 
We're migrating File API bugs to GitHub Issues; this one is: https://github.com/w3c/FileAPI/issues/19