W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: DOM Futures

From: Alex Russell <slightlyoff@google.com>
Date: Mon, 15 Jul 2013 15:46:40 +0100
Message-ID: <CANr5HFUyrHh2XVTZs+RgMmvUGYqs4m+Uz-q=VhGsbfuNBrjJeg@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: cowwoc <cowwoc@bbs.darktech.org>, Eric Rescorla <ekr@rtfm.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Anne van Kesteren <annevk@annevk.nl>
On Sun, Jul 14, 2013 at 10:34 PM, Bjoern Hoehrmann <derhoermi@gmx.net>wrote:

> * cowwoc wrote:
> > 3. Revisiting DOM Futures in light of the fact that the API has been
> >    officially frozen since our last meeting:
> >    http://lists.w3.org/Archives/Public/www-tag/2013Jun/0075.html
> Tab Atkins told people "The spec is done." already back in mid-april,
> http://lists.w3.org/Archives/Public/public-script-coord/2013AprJun/0146
> and much has changed since.

This is inaccurate. Very little has changed. Semantically, only one
corner-case is handled differently, and even then only in an observable way
under special conditions. The naming has changed for some methods, but this
was anticipated and indicates EVEN GREATER stability as it has been
accepted by both TC39 and in the draft DOM spec.

We should, however, expect to see continued *additions* to the set of
static methods on the Promise object.

Your mis-characherization of the state of the proposal may lead to your
conclusion, in which case it might be worth re-visiting it.

> Considering that the W3C has not published
> any draft at all with the proposed API, you would have to assume that
> the whole W3C process consists of nothing but rubberstamping and typo
> correction in order to consider it "officially frozen". That might be
> unwise.
Received on Monday, 15 July 2013 14:47:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:49 UTC