- From: Arun Ranganathan <arun@mozilla.com>
- Date: Thu, 31 Oct 2013 11:33:11 -0400
- To: Arthur Barstow <art.barstow@nokia.com>, Web Applications Working Group WG <public-webapps@w3.org>
- Cc: psweatte <psweatte@sonic.net>
Note that all LC Commentary, including that sent on this listserv, is tracked here: http://www.w3.org/wiki/Webapps/LCWD-FileAPI-20130912 -- A* On Oct 31, 2013, at 9:12 AM, Arthur Barstow wrote: > Hi, > > For the purposes of tracking your comments for the September 12 File API Last Call Working Draft, please let us know if Arun's reply is satisfactory or not. In the absence of a reply from you by November 7, we will assume Arun's reply is OK with you. > > -Thanks, ArtB > > On 10/23/13 6:04 PM, ext Arun Ranganathan wrote: >> Hi there! >> >> >> On Oct 23, 2013, at 12:32 PM, psweatte wrote: >> >>> 7.2 Interface File: >>> -add creationDate property >> >> Thanks for your feedback. *Most* filesystems don't really have a creation time. While Windows does, Unix-style OS return the *change time" or last modified time. Since we want fidelity with OS filesystems wherever possible, I'm not sure this is a viable property to add. >> >> >>> -add size property >> This already exists via the inheritance relationship with Blob. >> >> >>> -If the last modification date and time are not known, the attribute must return an empty string >> >> Currently the spec says to return the current date and time. It's a Date not a String. >> >> >>> 8.3. Event Handler Attributes >> >> I think the current set of event handler attributes is sufficient, especially given the backdrop of event models in general not being the best way to asynchronously access large data sets such as File and Blob. >> >> >>> -add onNotfounderror event handler >>> -add onReaderror event handler >>> -add onSecurityerror event handler >>> -add onHTTPerror event handler >>> -add onSelectfrombrowse event handler >>> >>> >>> >> > >
Received on Thursday, 31 October 2013 15:33:40 UTC