W3C home > Mailing lists > Public > www-tag@w3.org > April 2015

Re: Permission API Review: Fwd: [blink-dev] Intent to Ship: Permissions API

From: Daniel Appelquist <appelquist@gmail.com>
Date: Tue, 7 Apr 2015 15:12:49 +0100
Cc: Alex Russell <slightlyoff@google.com>
Message-Id: <CB6D93CD-1E75-4C1F-90B4-8DF1E8685E40@gmail.com>
To: TAG List <www-tag@w3.org>
Alex - should we use this week’s call to cover this topic / finalize and agree the feedback?

Thanks,
Dan

> On 6 Apr 2015, at 23:16, Alex Russell <slightlyoff@google.com> wrote:
> 
> Hey all,
> 
> Per previous conversations, it looks like now would be a great time for others here to give our draft feedback on the Permissions API a look:
> 
>     https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>
> 
> Regards
> 
> ---------- Forwarded message ----------
> From: Alex Russell <slightlyoff@google.com <mailto:slightlyoff@google.com>>
> Date: Mon, Apr 6, 2015 at 3:15 PM
> Subject: Re: [blink-dev] Intent to Ship: Permissions API
> To: Marcos Caceres <marcos@marcosc.com <mailto:marcos@marcosc.com>>
> Cc: Dimitri Glazkov <dglazkov@chromium.org <mailto:dglazkov@chromium.org>>, Philip Jägenstedt <philipj@opera.com <mailto:philipj@opera.com>>, Elisabeth Morant <egm@google.com <mailto:egm@google.com>>, Philip Rogers <pdr@chromium.org <mailto:pdr@chromium.org>>, Mike West <mkwst@chromium.org <mailto:mkwst@chromium.org>>, Jake Archibald <jakearchibald@google.com <mailto:jakearchibald@google.com>>, blink-dev <blink-dev@chromium.org <mailto:blink-dev@chromium.org>>, Mounir Lamouri <mounir@lamouri.fr <mailto:mounir@lamouri.fr>>
> 
> 
> /me puts TAG hat on
> 
> I'm grateful for Mounir's work on updating the design based on feedback. I think it's getting better VERY quickly.
> 
> Given the time constraints, I spent some time over the weekend updating the TAG feedback based on the latest draft <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>. The other TAG members (and the list) need to weigh in (I'll circulate it today to get input ASAP), but I think it covers the bases.
> 
> The biggest issues are:
> The "string-ness" of the status value. I worry about the ability to model the full set of permissions without a more extensible type and it will be hard to retrofit later
> Lack of reflection for the majority of web platform permissions
> An inability to enumerate which permissions are supported by the API
> Regards
> 
> 
> On Mon, Apr 6, 2015 at 12:37 PM, Marcos Caceres <marcos@marcosc.com <mailto:marcos@marcosc.com>> wrote:
> 
> 
> 
> On April 3, 2015 at 5:28:23 PM, Dimitri Glazkov (dglazkov@chromium.org <mailto:dglazkov@chromium.org>) wrote:
> > Looking over W3C TAG activities, seems like they provided useful feedback
> > on the API: https://github.com/w3ctag/spec-reviews/issues/45 <https://github.com/w3ctag/spec-reviews/issues/45> and
> > https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>
> >
> > Have the issues mentioned been addressed?
> 
> I believe so. Mounir went through each issue raised and made modifications to the spec as needed. Not all recommendations were accepted by the Editors. Having said that, there is still time to iterate over the design as implementation/user experience is gained.
> 
> 
> 
> 


Received on Tuesday, 7 April 2015 14:13:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:11 UTC