I think that this mechanism, if adopted,cwould also be important in
resolving permissions to access output devices, as well as permissions to
enumerate device capabilities for either input or output.
I'm not trying to inject output back into the 1.0 scope here. I'm just
hoping that we do not make the mistake of designing a mechanism for media
input only and then having to retrofit concepts later.
...Joe
On Wed, Sep 2, 2015 at 8:43 PM, Mathieu Hofman <Mathieu.Hofman@citrix.com>
wrote:
> Thanks for the pointer.
>
> Harald said there to bring discussion to the list on how this should be
> implemented but it doesn't seem to have ever happened, so I guess here we
> go?
> Right now I don't really have an opinion on the How, but I think it'd be
> valuable to expose the gUM devices permissions in that API, one way or
> another.
>
> Mathieu
>
> > -----Original Message-----
> > From: Martin Thomson [mailto:martin.thomson@gmail.com]
> > Sent: Wednesday, September 02, 2015 5:29 PM
> > To: Mathieu Hofman
> > Cc: public-media-capture@w3.org
> > Subject: Re: Permissions API
> >
> > See https://github.com/w3c/permissions/issues/10
> >
> > On 2 September 2015 at 17:21, Mathieu Hofman
> > <Mathieu.Hofman@citrix.com> wrote:
> > > Hi all,
> > >
> > >
> > >
> > > I searched previous discussions but couldn’t find anything. Is there
> > > any plans to expose the audio/video/screen capture permissions granted
> > > by the user as part of the Permissions API [1].
> > >
> > > Right now an application could guess if it has permissions using the
> > > enumerateDevices and see if the label is blank or not, but that’s
> > > quite hacky.
> > >
> > >
> > >
> > > Mathieu
> > >
> > >
> > >
> > > [1] https://w3c.github.io/permissions/#permission-registry
>
--
. . . . . ...Joe
*Joe Berkovitz*
President
*Noteflight LLC*
49R Day Street / Somerville, MA 02144 / USA
phone: +1 978 314 6271
www.noteflight.com
"Your music, everywhere"