This repository has been archived by the owner on Dec 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 22
/
legacy.html
432 lines (429 loc) · 19.8 KB
/
legacy.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
<!DOCTYPE html>
<html lang="en">
<head>
<title>Is WebRTC ready yet?</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="WebRTC, Talky, WebAudio, SimpleWebRTC">
<link rel="stylesheet" type="text/css" href="//cloud.typography.com/7773252/712764/css/fonts.css">
<link rel="stylesheet" href="css/style.css">
</head>
<body>
<div class="content">
<section>
<h1>Is WebRTC ready yet?</h1>
<div id="support" class="card">
<h2>Browser support scorecard</h2>
<table>
<tr class="browsers">
<th> </th>
<th><img src="images/canary.png" alt="Chrome Canary" title="Chrome Canary"></th>
<th><img src="images/chrome.png" alt="Chrome" title="Chrome"></th>
<th><img src="images/opera.png" alt="Opera" title="Opera"></th>
<th><img src="images/nightly.png" alt="Firefox Nightly" title="Firefox Nightly"></th>
<th><img src="images/firefox.png" alt="Firefox" title="Firefox"></th>
<th><img src="images/bowser.png" alt="Bowser" title="Bowser"></th>
<th><img src="images/edge.png" alt="Edge" title="Microsoft Edge"></th>
<th><img src="images/safari.png" alt="Safari" title="Safari"></th>
</tr>
<tr class="versions">
<th></th>
<th>Canary</th>
<th>Chrome</th>
<th>Opera</th>
<th>Nightly</th>
<th>Firefox</th>
<th>Bowser</th>
<th>Edge</th>
<th>Safari</th>
</tr>
<tr>
<th class="feature"> <a href="#peerConn">PeerConnection API</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td title="using a shim" class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The basic building block for connecting to peers. Defined by the W3C WebRTC Working Group.</td>
</tr>
<tr>
<th><a href="#getUserMedia">getUserMedia</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The ability to request access to a user's webcam and microphone.</td>
</tr>
<tr>
<th><a href="#dataChannels">dataChannels</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Data channel support comes in two flavors: "reliable" means they are guaranteed to arrive and arrive in the correct order, "unreliable" means that order doesn't matter and dropped messages are acceptable.</td>
</tr>
<tr>
<th><a href="#turn">TURN support</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">TURN servers are necessary for situations where STUN fails to produce two addressable endpoints. Which is a fancy way of saying, "getting around firewalls."</td>
</tr>
<tr>
<th><a href="#echo">Echo cancellation</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">This may be the most subjective item in this list. 3 or 4 users should be able to use a service like Talky without headphones on and not experience feedback problems.</td>
</tr>
<tr>
<th><a href="#mediaStream">MediaStream API</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">When you request user media or get media from a peer it's held in a MediaStream object. Having the ability to add/remove and mute tracks it possible to do audio processing and control bandwidth consumption. </td>
</tr>
<tr>
<th><a href="#mediaConstraints" title="for bandwidth control">mediaConstraints</a></th>
<td class="inc"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The ability to specify restricted video sizes. This is important for bandwidth control. There are two aspects to this. The first is being able to specify constraints when first requesting access. The second is allowing you to apply constraints to an existing MediaStream.</td>
</tr>
<tr>
<th><a href="#multistream">Multiple Streams</a></th>
<td title="using 'Plan B'" class="inc"></td>
<td title="using 'Plan B'" class="inc"></td>
<td title="using 'Plan B'" class="inc"></td>
<td title="using 'Unified Plan'" class="yes"></td>
<td title="using 'Unified Plan'" class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The ability to transport multiple audio and video streams on the same peerconnection. This is important for transporting multiple streams from a centralized server or rebroadcasting streams from other peers.</td>
</tr>
<tr>
<th><a href="#simulcast">Simulcast</a></th>
<td class="inc"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="no"></td>
<td class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The ability to acquire media streams at multiple resolutions and framerates and send them to the peer. Chrome allows this through undocumented SDP mangling.</td>
</tr>
<tr>
<th><a href="#screenSharing">Screen Sharing</a></th>
<td title="requires an extension" class="inc"></td>
<td title="requires an extension" class="inc"></td>
<td title="requires an extension" class="inc"></td>
<td title="behind a whitelist." class="inc"></td>
<td title="behind a whitelist." class="inc"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The ability to request access to a MediaStream of the computer screen. This is crucial for feature parity with existing communication solutions. In Chrome, this requires an <a href="https://github.com/otalk/getScreenMedia/tree/master/chrome-extension-sample">extension</a>, in Firefox there is a whitelist maintained by Mozilla. It's understandable there are some security and privacy concerns around screen sharing as a feature, so browser vendors are stepping cautiously as they try to work out how this should be implemented.</td>
</tr>
<tr>
<th><a href="#rebroadcast">Stream re-broadcasting</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">In order to support some of the more interesting topologies for routing data, we need to be able to take a MediaStream object from one peer and add it to another PeerConnection. Without this, the only way of doing multi-user is a mesh network or a centralized server.</td>
</tr>
<tr>
<th class="feature"> <a href="#getStats">getStats API</a></th>
<td class="inc"></td>
<td class="inc"></td>
<td class="inc"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">The <a href="http://w3c.github.io/webrtc-stats/webrtc-stats">Statistics API</a> allows to query various information about the PeerConnection like the current bitrate, round trip time or the number of video frames decoded.</td>
</tr>
<tr>
<th class="feature"> <a href="#ortc">ORTC API</a></th>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">An alternative to the PeerConnection API defined by the W3C ORTC Community Group.</td>
</tr>
<tr>
<th><a href="#h264">H.264 video</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for H.264 video. A WebRTC compliant browser should support both H.264 and VP8 video.</td>
</tr>
<tr>
<th><a href="#vp8">VP8 video</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for VP8 video. A WebRTC compliant browser should support both H.264 and VP8 video.</td>
</tr>
<tr>
<th><a href="#interop">Solid interoperability</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Multiple browsers consistently being able to talk to each other is essential to making WebRTC a true web technology and not just something that makes for a nice demo. </td>
</tr>
<tr>
<th><a href="#srcobject">srcObject in media element</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">srcObject is the way to indicate to a video or audio element that it should play a MediaStream (createObjectURL is obsoleted in the standard and leaks streams until the document dies).</td>
</tr>
<tr>
<th><a href="#promisegum">Promise based getUserMedia</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">GetUserMedia has moved to mediaDevices (instead of hanging directly on navigator), and uses Promises instead of callbacks. In Chrome this was shimmed by <a href="https://github.com/webrtc/adapter">adapter.js</a>.</td>
</tr>
<tr>
<th><a href="#promisepc">Promise based PeerConnection API</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">According to the latest W3C specification Promises should be used instead of callbacks. Natively supported in Chrome and Firefox, shims in <a href="https://github.com/webrtc/adapter">adapter.js</a> are available for older versions (or Edge which does not include a native RTCPeerConnection.</a>
</tr>
<tr>
<th><a href="#webaudio">WebAudio Integration</a></th>
<td class="yes"></td>
<td title="input only" class="inc"></td>
<td title="input only" class="inc"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td title="input only" class="inc"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for modifying audio using WebAudio on both input and output is important.</td>
</tr>
<tr>
<th><a href="#mediarecorder">MediaRecorder Integration</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for recording video/audio media streams to a local blob rather than sending to a remote peer.</td>
</tr>
<tr>
<th><a href="#canvas">Canvas Integration</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="no"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for inserting generated or modified video into a MediaStream from a canvas. Important for funny hats (and sharing games, etc).</td>
</tr>
<tr>
<th><a href="#testing">Test support</a></th>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="yes"></td>
<td class="no"></td>
<td class="yes"></td>
<td class="no"></td>
</tr>
<tr class="about">
<th></th>
<td colspan="8">Support for commandline or javascript flags that use fake devices or files for getUserMedia and allow bypassing user prompts. This allows for automatic testing using services such as travis-ci which is <a href='http://rtc.io/testing-process.html'>described here</a>.</td>
</tr>
</table>
<h3>Completion Score: <span class="score"></span>%</h3>
</div>
<p>See an error? This site is open source on Github, so please let us know by <a href="https://github.com/webrtcftw/iswebrtcreadyyet.com/issues">opening an issue</a>.</p>
</section>
<section class="help cf">
<article>
<h2>You can help make WebRTC better for everyone—by using it.</h2>
<p>WebRTC is one of the most transformative additions to the web platform, but it's still early days.</p>
<p>There's a big difference between technology that makes for an interesting demo and what's needed for something that could work on par with existing video chat products.</p>
<p>That gap can be closed—and data can help browser developers championing these great features to close it faster.</p>
<h2>Here's how you can help:</h2>
<p><strong>
Use <a href="https://talky.io">Talky </a>the next time you have need for a web video chat, then submit the feedback form.</strong></p>
<p>All statistics are collected anonymously and will be reported publicly on this site.</p>
</article>
<aside><a href="http://talky.io" alt="Talky" class="talky-logo"></a>
<h3>Help test WebRTC now</h3>
<p>
Talky is built entirely on open-source, MIT-licensed <a href="http://simplewebrtc.com">SimpleWebRTC </a>toolkit.
</p>
<p>
SimpleWebRTC is intended to be fully interoperable with any signaling platform (open source servers like <a href="http://github.com/andyet/signalmaster">SignalMaster</a>, federated protocols like XMPP, and commercial products.)
</p>
<p>Teams at Mozilla and Google are actively using Talky to dogfood and improve their WebRTC implementations. </p>
</aside>
</section>
</div>
<script src="//ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js"></script>
<script src="http://static.andyet.com/tag.js"></script>
<script>
$(function () {
$('table').delegate('th a', 'click', function () {
$(this).parents('tr').next().slideToggle();
});
var yes = $('td.yes').length,
inc = $('td.inc').length,
no = $('td.no').length;
var score = ((yes + 0.5 * inc) / (yes + inc + no) * 100).toFixed(1);
$('span.score').text(score);
});
</script>
</body>
</html>