facingMode constraint does not work on Pixel phone |
|||||
Issue descriptionI have tested with https://jsfiddle.net/guidou/8e1cLn1j/ and the constraint works fine on most devices, but does not work on Pixel.
,
Aug 10 2017
It turns out that this was already fixed since Chrome 59. The problem is that I was testing with a Canary based on 57.
,
Aug 10 2017
Have you tried a pixel XL? I can not make this work.
,
Aug 10 2017
Reopening as per #3. I don't current have a Pixel XL available for testing. What Chrome version are you running? How does it fail?
,
Aug 10 2017
59 on 7.1. It fails in that it doesn't honor the facingMode constraint.
,
Aug 10 2017
How does it not honor it? Do you always get the front camera, always the back camera, always the opposite of what you request, a random one?
,
Aug 10 2017
I just got access to Pixel XL running Chrome 59 and Android 7.1.1 and the facingMode constraint works as expected, just like every other model I have tested. I just tested with https://jsfiddle.net/8e1cLn1j/10 and https://jsfiddle.net/8e1cLn1j/11 Can you provide a jsfiddle that fails on your phone?
,
Aug 10 2017
cgfarmer4@gmail.com: Please also try with the latest Chrome stable, which is Chrome 60.
,
Aug 10 2017
1. Chrome 60 is not available in the Play Store yet. Its only on the beta channel. 2. Your code works fine on 59. It doesn’t make sense to me why you call getUserMedia 2x though. This is what allows it to work. The API should only have to fire once. On August 10, 2017 at 7:55:10 AM, gui… via monorail ( monorail+v2.422849203@chromium.org) wrote: https://bugs.chromium.org/p/chromium/issues/detail?id=750701#c7
,
Aug 10 2017
cgfarmer4@: The script is just a minor variation of the script for bug 746534 , which you also reported. That bug involved two calls to getUserMedia and I did not bother removing the first call. Please also try with https://jsfiddle.net/guidou/9k41rg0b/2 and https://jsfiddle.net/guidou/9k41rg0b/3 which contain a single call and also work fine on the Pixel XL I'm using for testing. Chrome 59 stable or later should work fine. I asked you to run 60 just in case you were inadvertently running an early development version of 59. Also, can you provide a script where gUM fails on you Pixel XL to see if it also fails for me or to check if it's a bug in the application?
,
Aug 10 2017
It does appear this has been fixed since Chrome 59.I had last tested all of the use cases in 57 so that would coincide with your findings. Thank you for all your help and exhaustive testing with these couple bugs. On August 10, 2017 at 8:24:15 AM, gui… via monorail ( monorail+v2.422849203@chromium.org) wrote:
,
Aug 10 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by guidou@chromium.org
, Aug 3 2017