Tested this issue using reported version #59.0.3071.109 on Linux Ubuntu 14.04 and was unable to reproduce the issue as per the steps mentioned in original comment.

@shimi: Could you please find the attached screen cast and let us know if we missed any steps from our end. If possible please add a screenshot or screen cast for further investigation.

Thanks!!

Deleted: Jun 27 2017 3-21 PM.webm 7.1 MB

	Jun 27 2017 3-21 PM.webm 7.1 MB View Download

There is a missing step in your video. See my attached video. It starts with showing how the website should work (as it does with version 58) and continues showing how it fails after upgrading to version 59.

Deleted: letsgaze.webm 10.6 MB

	letsgaze.webm 10.6 MB View Download

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I'll take a look at this.
This might be related to spec-compliant video constraints in M59.

It works well for me on 59, 60 and 61.
The only way I could reproduce the problem as in the video on #3 is on a system without devices (without cameras or without microphones).

In this case, getUserMedia fails early in M59 and newer (as the spec says it should) instead of asking for permissions (as 58 wrongly does).
I suspect the application believes the getUserMedia error is because no permission was given when in fact the error is because there are no devices.

shimi.chen@: can you confirm that this is the case?
you can check https://guidou.github.io/enumdemo4.html to get a list of devices recognized by Chrome. If the list does not include at least one videoinput and one audioinput device, a getUserMedia request for video and audio should fail without asking for permissions.

I obviously had a microphone connected (or you could not hear me in the screencast), but not a webcam. I can confirm that it works on another computer, which has a webcam.

To be clear, getUserMedia fails by design if you don't have *both* a microphone *and* a camera?

getUserMedia fails by design if you request both, but don't have both.
If you only have a mic and request only audio, getUserMedia  will succeed. 
Similarly,  if you only have a camera and request only video, getUserMedia will suceed too. 
You can use enumerateDevices to determine if there are any microphones or cameras on the system. 

Closing the bug since this is working as intended.