4 ms·
I'm guessing that when Chrome added WebRTC last week (http://www.webrtc.org/blog/webrtcnowavailableinthechromedevchannel http://www.webrtc.org/blog/webrtcnowava
by ZeroGravitas 15y ago
I'm guessing that when Chrome added WebRTC last week (http://www.webrtc.org/blog/webrtcnowavailableinthechromedevchannel http://www.webrtc.org/blog/webrtcnowavailableinthechromedevc...} they only added VP8 encoding, so when Firefox adds it the numbers will skew even stronger toward WebM for native encoding.