+ tommi@/guidou@/hbos@/niklase@,  can anyone of you pls take a look and triage?

Unable to reproduce the issue on chrome reported version 65.0.3325.146 using Windows-10 surface pro with steps mentioned below:
1) Launched chrome reported version and navigated to URL: https://simplewebrtc.com/demo.html
2) Able to see "Allow" or "Block" pop-up on top left of browser.

@Reporter: Please find the attached screenshot for your reference and let us know if we missed anything in reproducing the issue. Try to test this issue by creating new person with no apps and extensions in it and let us know if the issue still persists.

Thanks!

Deleted: 819694.PNG 463 KB

	819694.PNG 463 KB View Download

Am I understanding it correctly that this fails on all browsers where it's supposed to work, not only Chrome?

If so, it sounds like the problem isn't with Chrome.

Please note that reported problem is only happening in latest: "Microsoft Surface Pro" which has rear/front camera.

- When i go to chrome://media-internals i can see camera;s available
- But when i go to website https://simplewebrtc.com/demo.html it still same. I do not get the allow or block popup and silently it keeps failing
- On that same PC. Chromium / Canary, Google chrome, Firefox, Opera none is able to use WebRTC.

Is there any settings i could check on Windows 10 to verify its not Google chrome issue at all? Is there any specific regedit or policy settings i can verify to confirm that its not caused by Google chrome?

Please see the video clip on that PC.  
on my next post.

If Firefox doesn't work either it points to a problem that is not specific to Chrome. Can you verify that?

Thank you for providing more feedback. Adding the requester to the cc list.

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

#8

- Firefox does not work either (node-webkit does not work either, my compiled chromium 46 and chromium nightly does not work either)
- Can anyone please share me extra manual checkup to verify why its failing and make sure its not caused by WebRTC?

Is there any tool, regedit entry, policy can be verified to validate the root cause why its happening, why VLC, Gstreamer, Microsoft Skype, camera test tools working but not WebRTC?

Thank you for providing more feedback. Adding the requester to the cc list.

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

WebRTC does not directly access the camera. The browser does. Chrome and Firefox have their own implementations for accessing the camera, independent of WebRTC.
Does https://webrtc.github.io/samples/src/content/getusermedia/gum/ work with any browser?

YES - on that PC. This works with all browsers:  https://webrtc.github.io/samples/src/content/getusermedia/gum/ 

But this https://simplewebrtc.com/demo.html fails with all browsers.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Then it's not an issue with the camera. What about
https://webrtc.github.io/samples/src/content/peerconnection/pc1/

- On that PC with all browsers "https://webrtc.github.io/samples/src/content/peerconnection/pc1/" works. 

- But on that same PC with all browser "https://simplewebrtc.com/demo.html" do not ask "Allow" or "Deny" popup. Fails always.

Thank you for providing more feedback. Adding the requester to the cc list.

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

looks like https://simplewebrtc.com/demo.html has been denied at some point and the preference has been stored. See the icon in the right side of the omnibar.

No it was not denied when i go to : chrome://settings/content/camera i do not see any blocked list nor allowed list  about "https://simplewebrtc.com/demo.html"

But i do see "https://webrtc.github.io/samples/src/content/peerconnection/pc1/" and 

@guidou/@tommi: Please have a look at comment#20 and help in triaging the issue.

Thanks!

It's not clear to me what the next steps are.  Is the below correct?

- The problem exists on a single machine
- (comment #17) On that machine, the webrtc.github sample works, but not simplewebrtc.
- simplewebrtc loads scripts from unauthenticated sources (unclear if that's causing problems)

From my perspective, it looks like Chrome is working fine but there might be website issues.

Please note

1. on `chrome://settings/content/camera` it does not show blocked list of `https://simplewebrtc.com/demo.html`. Even though the behaviour is exactly like it was blocked by user. (Therefore i was asking do we have any manual / alternative way to check if its blocked by the user using windows policy or registry entry?)

2. Please note i did uninstalled complete Google chrome and re-installed, tried resetting Google chrome over and over but `https://simplewebrtc.com/demo.html` had same behaviour on Google chrome, Chromium, Canary, Firefox, Opera

3. On same machine all the other's were working such as appr.tc, test.webrtc.org or https://webrtc.github.io/samples/src/content/peerconnection/pc1/

4. `chrome://media-internals` always showed the camera 

I still could not fully figured out what is the root cause of that only this: `https://simplewebrtc.com/demo.html` failed. 

I still believe that its a BUG related to `https://simplewebrtc.com/demo.html` only (very unknown) out of my knowledge. 

My wild guess is that the Microsoft latest surface pro or windows frame server has something to do with this issue?

The fact that Edge is also reported to fail points to a problem with the simplewebrtc website and not with Chrome.

As the issue is not reproducible from TE-end as per comment #4. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

@shamun: Can you upgrade the chrome to the latest and confirm if still available? Thank you!

#26

1. This problem that i reported was in a Surface pro which was purchased in United States. There the Surface pro failed with WebRTC

2. Recently in Europe we bought another brand new Surface Pro and with that all worked.

I do not have exact same Surface pro from the United states, i could not confirm but i can confirm that the European surface pro is compatible.

It must be something related to United States or only on that hardware. Please close the issue. If i face the issue once again i will request to re-open or post as new issue.

Thanks guys!!

Closing as per #27