-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semi accurate documentation #291
Comments
Fair point, but since is an easy error most users make, and many use Chrome, we thought that advising on the best practice to test this was easier. I'll check if and how I can revisit the docs to clarify your point when I get back home from the conference. |
Thank you for your quick replies 🔝 ! I was just at the verge of pulling my hair out because I wasn't sure how webRTC is implemented exactly. I'd say a oneliner would help people like me to get some orientation. |
This should be clearer, thanks for the feedback. |
As I was trying to find out the reason for this sentence:
I found out that (at least for streaming example) the aforementioned is valid only for UAs that doesn't implement srcObj property of HTMLMediaElement (i.e.
<video>
). Such UAs usecreateObjectURL
to create a blob URL and then assign it to<video>
.In case of Chrome (tested with version
43.0.2357.134 (64-bit)
)srcObj
is not implemented and since workers are not allowed to run locally (i.e.file://
scheme) the documentation is valid but in case of Firefox (tested with version39.0
) I was able to stream webcam video locally without delivering mystreamingtest.html
through a webserver (seeadapter.js
).The text was updated successfully, but these errors were encountered: