W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: Improve error message when browser denies access to getUserMedia()

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Wed, 24 Jul 2013 03:31:17 +0000
To: cowwoc <cowwoc@bbs.darktech.org>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1136080E1@xmb-aln-x02.cisco.com>

I think this will end up having privacy implications. For example, there was a bunch of discussion about the JS not being able to know if the user had selected a file or camera. 

Why would the JS need to know  the difference between these two ?


On Jul 9, 2013, at 11:16 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:

> Hi,
> 
> This is a follow-up discussion to https://code.google.com/p/chromium/issues/detail?id=257104
> 
> The WebRTC specification needs to provide a better error message in case the browser denies access to the camera, instead of the user. Currently, the specification states that 
> PERMISSION_DENIED is
>         the result of the user denying access. Instead of simply
>         modifying the definition of 
> PERMISSION_DENIED
>         to cover both cases, I propose splitting it into separate cases:
> 
> 
> 
>       
> 
> PERMISSION_DENIED_BY_USER
> 
>       
> 
> PERMISSION_DENIED_BY_BROWSER
> 
>       
> 
> 
> 
>       
> 
> Alternatively,
>         we need to add a String error message alongside the enum, and
>         require browsers to issue a different error message for each
>         case.
> 
> 
> 
>       
> 
> Thank
>         you,
> 
> Gili
Received on Wednesday, 24 July 2013 03:31:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:35 UTC