W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2013

Re: [whatwg] Web Notification: API inconsistency

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 23 Aug 2013 09:33:27 -0700
Message-ID: <CAAWBYDD02FkZGrsBkysn_OGnfAR4to9d1Xk1NJuHxsea1mOgpA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>, Jeremie Patonnier <jeremie.patonnier@gmail.com>
On Fri, Aug 23, 2013 at 6:16 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Fri, Aug 23, 2013 at 1:16 PM, Jeremie Patonnier
> <jeremie.patonnier@gmail.com> wrote:
>> The spec define two static methods: `requestPermission` and `get`
>> I'm a bit puzzled because `requestPermission` expect a callback function
>> where `get` return a `Promise`.
>
> It's not clear to me we can change the design of requestPermission()
> at this point. I think end-user notifications have been shipping for a
> while now... We could maybe upgrade it at some point to also return a
> promise, dunno.

If a function currently takes a callback argument and returns void,
it's trivial to upgrade it to instead make the callback optional and
return a promise when it's not passed.

~TJ
Received on Friday, 23 August 2013 16:34:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:23 UTC