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

Re: Permissions API vs local APIs

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 6 May 2015 17:39:29 +0200
Message-ID: <CADnb78iOmwnaKRaDaMy-JwB89KbU8Rq1CXvRERJ0TT9xabft=w@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>, Martin Thomson <mt@mozilla.com>, Doug Turner <dougt@mozilla.com>
Cc: Miguel Garcia <miguelg@chromium.org>, Michael van Ouwerkerk <mvanouwerkerk@google.com>, Mike West <mkwst@google.com>, WebApps WG <public-webapps@w3.org>, WebAppSec WG <public-webappsec@w3.org>
On Wed, May 6, 2015 at 5:33 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> I think Mozilla would be fine with taking the permission API as a
> dependency and implement that at the same time. Implementing the
> permission API should be fairly trivial for us.
>
> But we should verify this with the people actually working on the push API.
>
>> On Wed, May 6, 2015 at 10:59 AM, Michael van Ouwerkerk
>> <mvanouwerkerk@google.com> wrote:
>>> Yes, we wanted to ensure this is in the Push API because that seems to
>>> have more implementation momentum from browser vendors than the Permissions
>>> API. We didn't want developers to do hacky things in the meantime. I agree
>>> that once the Permissions API has critical mass, that should be the single
>>> place for checking permissions.

Martin, Doug?


-- 
https://annevankesteren.nl/
Received on Wednesday, 6 May 2015 15:40:04 UTC

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