W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2016

detecting the user agent webrtc implementation and version

From: Philipp Hancke <fippo@goodadvice.pages.de>
Date: Tue, 6 Dec 2016 13:18:08 +0100
To: public-webrtc@w3.org
Message-ID: <7b6fa7d3-2785-621e-8a83-620f786bdbbc@goodadvice.pages.de>
Should there be a way for the RTCPeerConnection to expose its 
implementation and version to the application?

Bear with me... I have quite a bit of code that attempts to detect the 
browser version (Chrome, Firefox, Edge) and browser version and does 
various workarounds based on that.

Currently the detection of the browser type is based on the existence of 
prefixed objects like mozRTCPeerConnection. See
I hope that the prefixed stuff is going away at some point but how do I 
know to activate a Firefox-workaround then?

Similary, the browser version is extracted from the user agent. Doing UA 
sniffing is even worse here. If I were to say "oh sorry, you are based 
on webrtc.org and using version 42 which is way to old" this could block 
all opera users. And I would really like to block old versions of Google 
Chrome which fail to parse UDP/TLS/RTP/SAVPF during setRemoteDescription.
Received on Tuesday, 6 December 2016 12:19:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:23 UTC