|
@@ -8,7 +8,7 @@ import * as StatisticsEvents from "../../service/statistics/Events";
|
8
|
8
|
/* Whether we support the browser we are running into for logging statistics */
|
9
|
9
|
var browserSupported = RTCBrowserType.isChrome() ||
|
10
|
10
|
RTCBrowserType.isOpera() || RTCBrowserType.isFirefox() ||
|
11
|
|
- RTCBrowserType.isNWJS();
|
|
11
|
+ RTCBrowserType.isNWJS() || RTCBrowserType.isElectron();
|
12
|
12
|
|
13
|
13
|
/**
|
14
|
14
|
* The LibJitsiMeet browser-agnostic names of the browser-specific keys reported
|
|
@@ -47,6 +47,8 @@ KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_OPERA] =
|
47
|
47
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_CHROME];
|
48
|
48
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_NWJS] =
|
49
|
49
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_CHROME];
|
|
50
|
+KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_ELECTRON] =
|
|
51
|
+ KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_CHROME];
|
50
|
52
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_IEXPLORER] =
|
51
|
53
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_CHROME];
|
52
|
54
|
KEYS_BY_BROWSER_TYPE[RTCBrowserType.RTC_BROWSER_SAFARI] =
|
|
@@ -327,6 +329,7 @@ StatsCollector.prototype._defineGetStatValueMethod = function (keys) {
|
327
|
329
|
case RTCBrowserType.RTC_BROWSER_CHROME:
|
328
|
330
|
case RTCBrowserType.RTC_BROWSER_OPERA:
|
329
|
331
|
case RTCBrowserType.RTC_BROWSER_NWJS:
|
|
332
|
+ case RTCBrowserType.RTC_BROWSER_ELECTRON:
|
330
|
333
|
// TODO What about other types of browser which are based on Chrome such
|
331
|
334
|
// as NW.js? Every time we want to support a new type browser we have to
|
332
|
335
|
// go and add more conditions (here and in multiple other places).
|