Hi,
We'd like to propose (and experiment in Webkit/chromium) exposing
dropped files/folders as {File,Directory}Entry defined in FileSystem
API [1] for better folders/files drag-and-drop support.
[1] File API: Directories and System http://www.w3.org/TR/file-system-api/
Usage scenario:
Many
On Tue, 15 Nov 2011 00:49:32 +0100, Aaron Colwell acolw...@chromium.org
wrote:
Hi,
I was looking at the seeking
algorithmhttp://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#seeking
and
had a question about step 10.
10. Wait until the user agent has established
On Thu, Nov 10, 2011 at 2:03 AM, Robert O'Callahan rob...@ocallahan.org wrote:
http://www.whatwg.org/specs/web-apps/current-work/#read-media
Can we allow the UA to add custom vendor-prefixed attributes to the html
and/or body elements? Alternatively, a vendor-prefixed class? We want to
be able
On Tue, Nov 15, 2011 at 5:21 PM, Jonas Sicking jo...@sicking.cc wrote:
Adding FileEntry/DirectoryEntry seems confusing since those are
generally writable in the FileSystem API spec, right? Additionally,
DirectoryEntry is asynchronous, which makes enumerating the tree more
painful.
The way
On Tue, Nov 15, 2011 at 2:07 PM, Robert O'Callahan rob...@ocallahan.org wrote:
So I propose that a toplevel class be set on the root element of a media
resource document in a toplevel browsing context.
While I'd normally object that classes are purely an author extension
point and UAs should
You could cheat by providing a 0 byte file folder/nul and define it
to not be created. On Windows (dos), such a file is used to test for
the existence of a directory, and it's illegal to create a file by
that name.
On 11/15/11, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Nov 15, 2011 at 1:01
On Wed, Nov 16, 2011 at 12:06 PM, Tab Atkins Jr. jackalm...@gmail.comwrote:
On Tue, Nov 15, 2011 at 2:07 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
So I propose that a toplevel class be set on the root element of a
media
resource document in a toplevel browsing context.
While I'd
On Tue, Nov 15, 2011 at 3:29 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Wed, Nov 16, 2011 at 12:06 PM, Tab Atkins Jr. jackalm...@gmail.com
wrote:
On Tue, Nov 15, 2011 at 2:07 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
So I propose that a toplevel class be set on the root
Very well then, I propose that a toplevel attribute be added to the root
element of media resource documents in toplevel browsing contexts :-).
Rob
--
If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive
On Tue, Nov 15, 2011 at 4:05 PM, Robert O'Callahan rob...@ocallahan.org wrote:
Very well then, I propose that a toplevel attribute be added to the root
element of media resource documents in toplevel browsing contexts :-).
APPROVED, SHIP IT.
~TJ
1) video and audio tags need volume attribute.
I know that it's possible to manipulate the volume attribute with
javascript.
But many internet forums allow some HTML tags but prohibit javascripts.
If I was able to set the initial volume with volume attribute of video
and audio tags, I would be
Thanks for your comments,
On Wed, Nov 16, 2011 at 8:02 AM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Nov 15, 2011 at 5:21 PM, Jonas Sicking jo...@sicking.cc wrote:
Adding FileEntry/DirectoryEntry seems confusing since those are
generally writable in the FileSystem API spec, right?
On Tue, Nov 15, 2011 at 5:37 PM, crocket crockabisc...@gmail.com wrote:
1) video and audio tags need volume attribute.
I know that it's possible to manipulate the volume attribute with
javascript.
But many internet forums allow some HTML tags but prohibit javascripts.
If I was able to set
On Tue, Nov 15, 2011 at 8:38 PM, Kinuko Yasuda kin...@chromium.org wrote:
The async nature of DirectoryEntry makes the code longer,
but webapps can work on the files incrementally and can show
progress UI while enumerating. For the apps that may deal with
potentially huge folders providing
any thoughts about minimising the security implications on this?
it makes it extremely easy to jump on a machine, open a browser page,
select a sensitive folder and upload it all to a remote server
z
On Wed, Nov 16, 2011 at 1:06 PM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Nov 15, 2011 at
On Tue, Nov 15, 2011 at 9:37 PM, Zac Spitzer zac.spit...@gmail.com wrote:
any thoughts about minimising the security implications on this?
it makes it extremely easy to jump on a machine, open a browser page,
select a sensitive folder and upload it all to a remote server
It's meaningless to
On Wed, Nov 16, 2011 at 7:19 AM, Aaron Colwell acolw...@chromium.org wrote:
I'm just trying to
determine if we are intentionally requiring frame accurate seeking at this
point or am I just misinterpreting some part of the spec.
My understanding from the discussion at the time was that it was
On Wed, Nov 16, 2011 at 11:06 AM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Nov 15, 2011 at 8:38 PM, Kinuko Yasuda kin...@chromium.org wrote:
The async nature of DirectoryEntry makes the code longer,
but webapps can work on the files incrementally and can show
progress UI while enumerating.
On Tue, Nov 15, 2011 at 10:58 PM, Kinuko Yasuda kin...@chromium.org wrote:
Good point, we could do this synchronously in workers!
I think we already have one way to convert Entry to EntrySync:
we can get a URL from Entry (Entry.toURL()), send the URL to
the worker and get the EntrySync via
19 matches
Mail list logo
