Issue metadata
Sign in to add a comment
|
No way to detect that the OS has blocked access to the camera
Reported by
sasung...@gmail.com,
Aug 8 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Steps to reproduce the problem: 1. Give access to the camera to any application which is not Chrome (for example, open https://webrtc.github.io/samples/src/content/getusermedia/gum/ by Firefox and give permission to access the camera and the microphone) 2. In Chrome open https://jsfiddle.net/quwhu8vp/ and give permission to access the camera and the microphone What is the expected behavior? According to https://w3c.github.io/mediacapture-main/#dom-mediadevices-getusermedia, "If the user grants permission but a hardware error such as an OS/program/webpage lock prevents access, reject p with a new DOMException object whose name attribute has the value NotReadableError and abort these steps." What went wrong? webkitGetUserMedia succeeds with a stream Did this work before? N/A Chrome version: 51.0.2704.106 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Aug 10 2016
,
Aug 10 2016
This looks primarily about the behavior of getUserMedia. Someone involved in the implementation of that API should take a look.
,
Aug 10 2016
Thank you for responding, guys. It was my mistake to post this issue in this category. So, should I repost it in the appropriate one?
,
Aug 10 2016
Reclassifying as blink->getusermedia.
,
Aug 16 2016
I can repro this with Firefox nightly and Chrome 54.0.2824.0. I get a stream+video showing in Firefox and Chrome seems to think it gets a stream as well (no JS errors), but the image is just black. If I close Firefox and refresh the page in Chrome, video is displayed. Assigning to hta@ for further triage.
,
Apr 5 2017
,
Jun 27 2017
This is a duplicate of bug 651910 , which has already been fixed. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Aug 9 2016