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

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

From: Alex Russell <slightlyoff@google.com>
Date: Wed, 8 Apr 2015 08:59:15 -0700
Message-ID: <CANr5HFXRWy2yQNJyBwu2wjMp24RtLFRs_LfY0G-CFoxWLOhSbQ@mail.gmail.com>
To: Daniel Appelquist <appelquist@gmail.com>
Cc: TAG List <www-tag@w3.org>
Yes.

On Tue, Apr 7, 2015 at 7:12 AM, Daniel Appelquist <appelquist@gmail.com>
wrote:

> 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
>
> Regards
>
> ---------- Forwarded message ----------
> From: Alex Russell <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>
> Cc: Dimitri Glazkov <dglazkov@chromium.org>, Philip Jägenstedt <
> philipj@opera.com>, Elisabeth Morant <egm@google.com>, Philip Rogers <
> pdr@chromium.org>, Mike West <mkwst@chromium.org>, Jake Archibald <
> jakearchibald@google.com>, blink-dev <blink-dev@chromium.org>, Mounir
> Lamouri <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>
> wrote:
>
>>
>>
>>
>> On April 3, 2015 at 5:28:23 PM, Dimitri Glazkov (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 and
>> >
>> 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 Wednesday, 8 April 2015 16:00:13 UTC

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