W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2014

Re: [whatwg] Notifications: making requestPermission() return a promise

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 7 Oct 2014 11:33:55 -0700
Message-ID: <CAAWBYDDXutG6HE_ewtm67oEHQ=Hax+haG3v-f-ZAz9rCT0Lo0A@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Andrew Wilson <atwilson@google.com>, WHATWG <whatwg@whatwg.org>, Jake Archibald <jaffathecake@gmail.com>, Peter Beverloo <beverloo@google.com>, Jonas Sicking <jonas@sicking.cc>
On Sun, Oct 5, 2014 at 7:41 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Thu, Oct 2, 2014 at 10:13 PM, Domenic Denicola
> <domenic@domenicdenicola.com> wrote:
>> So we should make a choice, as to whether we want developers to assume they will always get permission (in which case it should reject upon permission not being granted), or whether we want developers to ask the API whether they were granted permission (in which case it should give back a boolean fulfillment value or similar).
>
> How can they assume permission is always granted? It's up the user.
> It's a request from the developer and the user can say no. What's
> unclear about the name?

Yeah, you misunderstood the question.  It's about whether permission
failure should reject the promise or accept it with a boolean.

~TJ
Received on Tuesday, 7 October 2014 18:34:41 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:24 UTC