You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Some of the samples use new browser features. They may only work in Chrome Canar
8
8
9
9
All of the samples use [adapter.js](https://github.com/webrtc/adapter), a shim to insulate apps from spec changes and prefix differences. In fact, the standards and protocols used for WebRTC implementations are highly stable, and there are only a few prefixed names. For full interop information, see [webrtc.org/web-apis/interop](http://www.webrtc.org/web-apis/interop).
10
10
11
-
In Chrome and Opera, all samples that use `getUserMedia()` must be run from a server. Calling `getUserMedia()` from a file:// URL will work in Firefox, but fail silently in Chrome and Opera.
11
+
In Chrome and Opera, all samples that use `navigator.mediaDevices.getUserMedia()` must be run from a server. Calling `navigator.mediaDevices.getUserMedia()` from a file:// URL will work in Firefox, but fail silently in Chrome and Opera.
12
12
13
13
[webrtc.org/testing](http://www.webrtc.org/testing) lists command line flags useful for development and testing with Chrome.
0 commit comments