In what sense? It is a browser. It needs to support WebRTC 1.0. But its support of it is less of a concern to most (most developers I know focus first on Chrome and Safari and even Safari was left out of this article).

Nice catch Steve – fixed it.

Thanks for these additions Alex.

As far as I understand, the KITE set of tests aren’t enough and more need to be written to make it to the PR stage. I am sure work towards that goal is being done. Not sure at what pace though.

As reporting to the W3C WG about testing, I officially asked that question to Dominique in 2016 at the Technical Plenary Meeting in Lisbon. The concern was that chromium, firefox and safari where using the same underlying stack (webrtc.org). The answer is that, as far as W3C is concerned, only the implementation OF THE JS API matters, even if the underlying implementation is the same. In that regard, firefox, safari and chromium JS API are implemented sufficiently differently to fulfil W3C requirements.

“That third one of interoperability testing? With a test suite. That tests for the various features?”

At the same meeting, and for the reason you present (moving to CR), the question of the interoperability testing has been addressed. The Design of KITE has been presented and soon thereafter google agreed to sponsor it. KITE has been used for interoperability testing of all browsers, desktop and mobile, on a daily basis since availability. Corresponding results are visible on the webrtc.org page.

Today, chrome and safari are using it internally for their tests as well, and edge is evaluating it. At Kranky Geek in late 2018, Microsoft through the voice of James Cad, has announced using KITE for testing their UWP builds (tablets, Hololens, Xbox, …). INTEL has officially announced at TPAC in November 2018 their intend to open source their WebRTC Test suite, merge it in KITE, and use KITE moving forward.