On Wed, 19 Sep 2012, Adam Barth wrote:
On Wed, Sep 19, 2012 at 1:46 PM, James Graham jgra...@opera.com wrote:
On Wed, 19 Sep 2012, Edward O'Connor wrote:
Olli wrote:
I think we should discuss about moving File API: Directories and
System API from Recommendation track to Note.
Sounds good
On Wed, Sep 19, 2012 at 11:50 PM, James Graham jgra...@opera.com wrote:
On Wed, 19 Sep 2012, Adam Barth wrote:
On Wed, Sep 19, 2012 at 1:46 PM, James Graham jgra...@opera.com wrote:
On Wed, 19 Sep 2012, Edward O'Connor wrote:
Olli wrote:
I think we should discuss about moving File API:
On Wed, Sep 19, 2012 at 11:00 AM, Boris Zbarsky bzbar...@mit.edu wrote:
I was looking at http://dvcs.w3.org/hg/**undomanager/raw-file/tip/**
undomanager.htmlhttp://dvcs.w3.org/hg/undomanager/raw-file/tip/undomanager.htmland
ran into some issues:
1) No mention of where feedback should be
On 9/20/12 3:25 PM, Ryosuke Niwa wrote:
I guess. The tricky part is that almost all methods and properties on
DOMTransaction are optional. Do you know how one might specify a methods
on a callback interface to be optional?
I'm not sure you can, really. But you can specify them to be nullable,
Given that .item() returns a new object every time, I don't see the use
cases for returning an IDL array object. On the other hand, there are
drawbacks (e.g. it's not an actual JS array, unlike sequence). Are
there any particular reasons this is returning an IDL array object?
If there
On Wed, Sep 19, 2012 at 11:50 PM, James Graham jgra...@opera.com wrote:
On Wed, 19 Sep 2012, Adam Barth wrote:
On Wed, Sep 19, 2012 at 1:46 PM, James Graham jgra...@opera.com wrote:
On Wed, 19 Sep 2012, Edward O'Connor wrote:
Olli wrote:
I think we should discuss about moving File
+1
I don't see an indication of any major browser but Chrome planning to implement
this and expose it to the Web.
- Maciej
On Sep 18, 2012, at 4:04 AM, Olli Pettay olli.pet...@helsinki.fi wrote:
Hi all,
I think we should discuss about moving File API: Directories and System API
from
A new Candidate Recommendation of the WebSocket API was published on
September 20 and that resulted in a Call for Implementations [CfI]:
http://www.w3.org/TR/2012/CR-websockets-20120920/
The root of the test suite for this spec follows. Currently, the test
suite consists of submissions from
At http://www.w3.org/TR/xbl/#status-of-this-document, the following
message appears:
Beware. This specification is no longer in active maintenance and
the Web Applications Working Group does not intend to maintain it
further. No browser vendor has plans to implement this specification
