W3C home > Mailing lists > Public > public-webappsec@w3.org > May 2015

Re: Permissions API vs local APIs

From: Miguel Garcia <miguelg@chromium.org>
Date: Wed, 6 May 2015 18:05:15 +0100
Message-ID: <CAGTrua1oWbqg7od8vMpJB5WmkU4BA1y-Rhz=eBqe6oKC=sgxxA@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Doug Turner <dougt@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, Martin Thomson <mt@mozilla.com>, Michael van Ouwerkerk <mvanouwerkerk@google.com>, Mike West <mkwst@google.com>, WebApps WG <public-webapps@w3.org>, WebAppSec WG <public-webappsec@w3.org>
Is there a timeline for the permission API in Mozilla?

On Wed, May 6, 2015 at 5:58 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Wed, May 6, 2015 at 6:34 PM, Miguel Garcia <miguelg@chromium.org>
> wrote:
> > Notifications has it (as a property instead of a method which is a pain).
>
> Notifications is a special snowflake though since it has a
> requestPermission() method too which no other API that requires
> permission (e.g. geolocation, fullscreen, pointer lock) has today. The
> Notifications API predates a general Permissions API but is otherwise
> largely identical.
>
>
> > I think that once the permissions API has shipped in both Mozilla and
> Chrome
> > we should get future APIs to use it exclusively. Push seems to be a bit
> > border line given the timeline so I think we should just implement in
> both
> > places.
>
> Given that Doug seems okay with shipping this as part of the
> Permissions API (which won't wait until 2017, at least not the query()
> part) I'm led to the opposite conclusion.
>
>
> --
> https://annevankesteren.nl/
>
Received on Friday, 8 May 2015 02:25:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:13 UTC