RE: Updates to File API

2010-06-22 Thread Adrian Bateman
On Tuesday, June 22, 2010 8:40 PM, David Levin wrote: > I agree with you Adrian that it makes sense to let the user agent figure > out the optimal way of implementing origin and other checks. > > A logical step from that premise is that the choice/format of the > namespace specific string should b

Re: Updates to File API

2010-06-22 Thread David Levin
On Tue, Jun 22, 2010 at 7:58 PM, Adrian Bateman wrote: > On Tuesday, June 22, 2010 3:37 PM, Arun Ranganathan wrote: > > On 6/22/10 8:44 AM, Adrian Bateman wrote: > > > I think it makes more sense for the URL to be opaque and let user > > > agents figure > > > out the optimal way of implementing or

RE: Updates to File API

2010-06-22 Thread Adrian Bateman
On Tuesday, June 22, 2010 3:37 PM, Arun Ranganathan wrote: > On 6/22/10 8:44 AM, Adrian Bateman wrote: > > I think it makes more sense for the URL to be opaque and let user > > agents figure > > out the optimal way of implementing origin and other checks. > > I think it may be important to define:

Bubbling/Capturing for XHR + other non-DOM objects

2010-06-22 Thread Travis Leithead
Hi webapps and DOM events folks! (Cross-posting this) This topic came up internally on the IE team, and we thought it would be noteworthy to put this question before the working groups in hopes of getting a spec clarification made. The question is: for XHR and other non-DOM related objects tha

Re: Transferring File* to WebApps - redux

2010-06-22 Thread Eric Uhrhane
On Fri, Jun 18, 2010 at 10:53 AM, SULLIVAN, BRYAN L (ATTCINW) wrote: > Eric, > Based upon your responses there are a couple of additional things we > need to check on, but I'll look deeper into the current specs for the > things that should already be supported. > > The additional things are: > >

Re: Updates to File API

2010-06-22 Thread Arun Ranganathan
On 6/22/10 8:44 AM, Adrian Bateman wrote: On Friday, June 11, 2010 11:18 AM, Jonas Sicking wrote: On Fri, Jun 11, 2010 at 11:11 AM, Jonas Sicking wrote: On Fri, Jun 11, 2010 at 9:09 AM, Adrian Bateman It's not clear to me the benefit of encoding the origin into the URL. Do w

Re: [fileapi] urn -> URL

2010-06-22 Thread Alexey Proskuryakov
12.11.2009, в 0:13, Anne van Kesteren написал(а): It would however be consistent with WebSocket.URL, type="url">, url("image"), EventSource.URL, HTMLDocument.URL, etc. Keeping the author-facing APIs the same would be a good thing IMO. EventSource.URL and WebSocket.URL have been renamed in t

RE: Updates to File API

2010-06-22 Thread Adrian Bateman
On Friday, June 11, 2010 11:18 AM, Jonas Sicking wrote: > On Fri, Jun 11, 2010 at 11:11 AM, Jonas Sicking wrote: > > On Fri, Jun 11, 2010 at 9:09 AM, Adrian Bateman > >> It's not clear to me the benefit of encoding the origin into the URL. Do > >> we expect script to parse out the origin and use

[indexedDB] spec update

2010-06-22 Thread Andrei Popescu
Hi, Just a quick note that the structure of the IndexedDB spec has slightly changed after my fix to: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9790 The main changes are: - Dropped the "Request" suffix from the async API - Dropped the base classes (IDBDatabase, IDBObjectStore, etc) - Slightl

[Bug 9790] Request is not a good suffix for all the async interfaces in IndexedDB

2010-06-22 Thread bugzilla
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9790 Andrei Popescu changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|