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

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

From: Rob Manson <roBman@mob-labs.com>
Date: Fri, 26 Jul 2013 12:05:41 +1000
Message-ID: <51F1D975.6000300@mob-labs.com>
To: public-webrtc@w3.org
I just upgraded Chrome on my Linux laptop and this version is throwing 
PERMISSION_DENIED - for both "user denied" and "cached denial".

So latest versions of both FF and Chrome do seem to be following the 
spec for this scenario...although there are fine detail differences 
here...but meh.


On 26/07/13 11:46, Silvia Pfeiffer wrote:
> On Fri, Jul 26, 2013 at 9:55 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>> On 25/07/2013 7:43 PM, Rob Manson wrote:
>>> +1 to that (as long as DEVICE_NOT_AVAILABLE includes both system errors
>>> and truly "not available" so it doesn't provide a fingerprinting issue).
>>> Also, thanks for pointing out where the PERMISSION_DENIED came from Silvia
>>> 8) I was looking in the wrong spec (must have been tired).
>>> So in this case the bug should be filed with Chrome and not Firefox. From
>>> my tests the latest version of Chrome doesn't return PERMISSION_DENIED.
>>      We can't file a bug with Chrome until the spec adds the new enum. So
>> assuming there is consensus, we'd still have to wait for this to make it
>> into the editor's draft.
> FYI: PERMISSION_DENIED is in the spec:
> http://dev.w3.org/2011/webrtc/editor/getusermedia.html#idl-def-NavigatorUserMediaError
> Cheers,
> Silvia.
Received on Friday, 26 July 2013 02:06:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:50 UTC