Re: [File API] abort()

2010-12-06 Thread Arun Ranganathan
Anne, > On Fri, 03 Dec 2010 16:43:00 +0100, Arun Ranganathan > wrote: > > - Original Message - > >> Per http://dev.w3.org/2006/webapi/FileAPI/#abort invoking abort() > >> always > >> results in events getting dispatched. This is not what happens in > >> e.g. > >> Gecko at the moment. When

Re: Seeking status of Server-sent Events, Web Storage and Web Workers

2010-12-06 Thread Ian Hickson
On Mon, 6 Dec 2010, Charles Pritchard wrote: > On 12/6/2010 1:08 PM, Ian Hickson wrote: > > On Mon, 6 Dec 2010, Arthur Barstow wrote: > > > Since Hixie is active on HTML, perhaps someone else is willing to pick > > > one of these LCs and to review the issues, bugs, diffs, etc. and propose > > > the

Re: Seeking status of Server-sent Events, Web Storage and Web Workers

2010-12-06 Thread Ian Hickson
On Mon, 6 Dec 2010, Arthur Barstow wrote: > > Since Hixie is active on HTML, perhaps someone else is willing to pick > one of these LCs and to review the issues, bugs, diffs, etc. and propose > the next step . Any volunteers? I am responding to feedback on these specs, just not on the schedule

Re: using BlobBuilder append method with generated binary data

2010-12-06 Thread Paul Kinlan
That's what I thought when I first looked at it, however you can pre-set the array length and then iterate over every byte and set it. It is not ideal, but works. I have it running on http://appmator.appspot.com/ but it basically boils down to the following: var ui8a = new Uint8Array(output.lengt

Re: using BlobBuilder append method with generated binary data

2010-12-06 Thread Toni Ruottu
I do not think UInt8Array has any data. It is just a view for accessing the buffer. --Toni On Sat, Dec 4, 2010 at 1:12 AM, Paul Kinlan wrote: > I might have missed something but for appending client-side generated > data to a blob can't you just append a UInt8Array as that is based off > Array

Re: continue as a reserved word and a conflict with IndexedDB

2010-12-06 Thread Charles Pritchard
Should the spec have notes referring to the fact that it requires ECMA5 conformance or parse errors may result? I'm bringing this up regarding backward compatibility, as reserved words, if not escaped, lead to parse errors. Somewhat useful table: http://kangax.github.com/es5-compat-table/ It

[eventsource] Some data re Server-sent Events LC

2010-12-06 Thread Arthur Barstow
Re event-source spec, a few weeks ago I: reviewed the Bug list, reviewed e-mails submitted to public-webapps re the Dec 2009 LC and compared the LC version with the latest ED. I did not review WHATWG Issues for this spec [Issues] because I didn't know it existed. = Bugzilla: 4 bugs filed: 3 Fi

Re: Seeking status of Server-sent Events, Web Storage and Web Workers

2010-12-06 Thread Arthur Barstow
OK, so coming back to the what's next for these 3 LC documents question [Head] ... All of these specs have a Bugzilla component for issue and comment tracking, all are included in the WHATWG issue tracker at [Issues], all of the specs have changed since their LC was published and all of the

Re: continue as a reserved word and a conflict with IndexedDB

2010-12-06 Thread Oliver Hunt
This should work fine in a nightly already, if it doesn't you need to file a bug. --Oliver On Dec 6, 2010, at 3:08 AM, Jeremy Orlow wrote: > I'm pretty sure this was discussed and that EMCA5 does make it possible to > use continue as we do. At least that's the conclusion we had with delete.

Re: [File API] abort()

2010-12-06 Thread Anne van Kesteren
On Fri, 03 Dec 2010 16:43:00 +0100, Arun Ranganathan wrote: - Original Message - Per http://dev.w3.org/2006/webapi/FileAPI/#abort invoking abort() always results in events getting dispatched. This is not what happens in e.g. Gecko at the moment. When the state is EMPTY the method simpl

Re: continue as a reserved word and a conflict with IndexedDB

2010-12-06 Thread Jeremy Orlow
I'm pretty sure this was discussed and that EMCA5 does make it possible to use continue as we do. At least that's the conclusion we had with delete. My guess is that the JavaScriptCore (WebKit's main JavaScript engine) parser needs to be changed. If so, you should probably file a bug at webkit.o