On 09/20/2012 11:45 PM, Darin Fisher wrote:
File path information is already exposed via input type=file multiple.
File names may contain partial paths.
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#concept-input-type-file-selected
I couldn't
On 9/20/12 8:24 PM, ext Samuel Bronson wrote:
This does not make it clear why the specification was abandoned, or
say where more recent efforts in this area are focused; I suggest
changing it to something more like:
Thanks for the suggestion. If/when we publish that document again, I
will
The spec currently says[1]:
The value of the “prototype” property of an interface object for a
non-callback interface MUST be an object called the interface
prototype object.
At the same time, we have specs like File API defining things like this:
partial interface URL {
}
From: Boris Zbarsky [mailto:bzbar...@mit.edu]
The spec currently says[1]:
The value of the prototype property of an interface object for a
non-callback interface MUST be an object called the interface
prototype object.
At the same time, we have specs like File API defining
On 9/21/12 12:39 PM, Travis Leithead wrote:
I believe that firstly, the File API spec needs to be rationalized against the
URL API
They're already there. File API explicitly says that if you support URL
API then you get a normal interface object and proto object.
Once that happens, I
No comment on the value of DirectoryEntry for enabling asynchronous listing
of files in input type=file multiple?
-Darin
On Thu, Sep 20, 2012 at 4:48 PM, Maciej Stachowiak m...@apple.com wrote:
+1
I don't see an indication of any major browser but Chrome planning to
implement this and
On Fri, Sep 21, 2012 at 1:14 AM, James Graham jgra...@opera.com wrote:
On 09/20/2012 11:45 PM, Darin Fisher wrote:
File path information is already exposed via input type=file multiple.
File names may contain partial paths.
http://www.whatwg.org/specs/**web-apps/current-work/**
Or.. drag-n-drop receipt of a folder or set of folders.
On Fri, Sep 21, 2012 at 3:50 PM, Darin Fisher da...@chromium.org wrote:
No comment on the value of DirectoryEntry for enabling asynchronous
listing of files in input type=file multiple?
-Darin
On Thu, Sep 20, 2012 at 4:48 PM, Maciej
While I don't see any other browsers showing interest in implementing
the FileSystem API as currently specced, I do see Firefox coming
around to the belief that a filesystem-style API is a good thing,
hence their DeviceStorage API. Rather than scrap the API that we've
put 2 years of discussion
I like the idea of offering asynchronous listing of files in input type=file
multiple. But I think Filesystem API is overkill for this use case.
Regards,
Maciej
On Sep 21, 2012, at 3:50 PM, Darin Fisher da...@chromium.org wrote:
No comment on the value of DirectoryEntry for enabling
My personal objections (ones that I think are shared by at least some other
Safari folks):
- It's way too complicated. (As one crude metric, I count 22 interfaces; and
yes, I know many of those are callback interfaces or sync versions of
interfaces; it still seems overengineered).
- I see
On Fri, Sep 21, 2012 at 5:37 PM, Maciej Stachowiak m...@apple.com wrote:
My personal objections (ones that I think are shared by at least some other
Safari folks):
- It's way too complicated. (As one crude metric, I count 22 interfaces; and
yes, I know many of those are callback interfaces
12 matches
Mail list logo
