- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Sat, 21 Apr 2018 12:57:06 +0200
- To: public-webrtc@w3.org
On 04/20/2018 08:50 PM, Bernard Aboba wrote: > Dom said: > > "I have also noticed this reports wrong data for RTCDataChannel and filed > a bug accordingly https://github.com/GoogleChromeLabs/confluence/issues/276" > > [BA] The reports also doe not take into account any interfaces provided by adapter.js. > > So for example, the table indicates that Edge doesn't support RTCDTMFSender which adapter.js shims on top of "RTCDtmfSender". If we want to have counted cases like the adapter.js shim, I think we need to have separate columns for "browser" and "browser + adapter". What's the update process for this table? I note that replaceTrack from Chrome 65 is included, but not the dtmf attribute, which landed in 66, isn't. -- Surveillance is pervasive. Go Dark.
Received on Saturday, 21 April 2018 10:57:43 UTC