3 ms·
And here's to hoping they are able to push for the same thing for getUserMedia and the device motion/accelerometer APIs as well!
by Klathmon 11y ago
And here's to hoping they are able to push for the same thing for getUserMedia and the device motion/accelerometer APIs as well!
- asherkin 11y agogetUserMedia was killed off for insecure origins quite a while ago in Chrome.
- Klathmon 11y agoOh shit really? That's awesome!
- randall 11y agoI think it was Chrome 48. It also doesn't work for localhost.
- Klathmon 11y agoLocalhost is considered secure context, so it should still work for that... It won't work with file:/// urls, but localhost is fine. At least it was for me in 49 a couple weeks ago.
- artursapek 11y agoIt would be pretty hard to use the API if you couldn't test your code on localhost :P
- nfriedly 11y agoI think you're mistaken about localhost, this works fine for me on localhost:3000 navigator.getUserMedia({ video: true, audio: true }, console.log.bind(console, 'success'), console.log.bind(console, 'error') ); Chrome v50.0.2661.94 (64-bit) on OS X