On Tue, Aug 14, 2012 at 4:51 PM, Charles Pritchard wrote:
> Is there a long term plan for transferring access to Files from the
> FileSystem?
>
> Currently, we can using FileEntry.file semantics then post the resulting
> Blob to another frame. From that point, the receiver can create a Blob URL.
Please note that there's one other issue outstanding: both microtasks and
stable states are very closed, but neither may be what this needs. A
separate hook may be needed.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16790#c13.
On Tue, Aug 14, 2012 at 4:37 PM, Feras Moussa wrote:
> In genera
Is there a long term plan for transferring access to Files from the FileSystem?
Currently, we can using FileEntry.file semantics then post the resulting Blob
to another frame. From that point, the receiver can create a Blob URL. I'm
concerned about all the extra work with Blobs which may get stu
In general we are OK with changing it to the autoRevoke behavior below, but
have some concerns around changing the default behavior.
Changing the default behavior is a breaking change and any apps which expect
the URL to work multiple times will now be broken. In Windows 8, we also
implemented
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18558
Summary: [IndexedDB] Define error seen when key generator
maximum value is reached
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: N
TL;DR: Conway's law is already validated in this instance, but maybe
there's no real harm, and stuff to like about the proposal anyway. On
balance I think it is a good idea. (Plus a lot of stuff about @supports
...)
On Tue, 14 Aug 2012 01:59:28 +0200, Tab Atkins Jr.
wrote:
On Mon, Aug 1
On Mon, 13 Aug 2012 20:19:29 +0200, Tab Atkins Jr.
wrote:
The CSSWG would like to add a new top-level object called "CSS" that
we can hang several functions and constructors off of, so that we can
avoid the excessive verbosity that's probably required if we just put
everything on window
Coo
