1898941 - events.webinar.ru - Firefox is not a supported browser

Status: ASSIGNED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Ksenia Berezina [:ksenia]]

Environment:
Operating system: Linux
Originally reported Firefox version: Firefox 112.0
Last reproduced with the following UA: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Platforms reproduced on: windows,mac,linux,android

Steps to reproduce:
Previously it was possible to connect to, view, listen, chat, speak, stream in the online meetings, now it is not possible, because firefox now listed as an unsupported browser. Changing ua does not help.
https://help.webinar.ru/ru/articles/1518973-%D1%82%D0%B5%D1%85%D0%BD%D0%B8%D1%87%D0%B5%D1%81%D0%BA%D0%B8%D0%B5-%D1%82%D1%80%D0%B5%D0%B1%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F#h_c602a6acf1

Actual Behavior:
Firefox is listed as an unsupported browser

Created from https://github.com/webcompat/web-bugs/issues/121871

Comment 1

[Daniel Holbert [:dholbert]]

This quote from comment 0...

Changing ua does not help.

...was from the anonymous reporter, as of May 6 2023. Whether or not that statement was accurate at that point, it's not accurate now at least.

Testing today, changing UA does help. The site's WebRTC test page is at https://events.webinar.ru/support/test-webrtc and it seems to work fine if I spoof a Chrome UA string with e.g. https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher/

Looking at their JS when I load the page without UA-spoofing, it seems we're being judged as unsupported in this part of the site's JS, which is just UA-sniffing:

function checkHost(et) {
[...]
            ei = en.unblockUnsupportedBrowsers;
[...]
                eA = navigator.userAgent,
[...]
                eT = eA.match(/firefox\/(([0-9]\.?)+)/i),
[...]
    } else eT ? ei ||
                eu('ProductNotSupportedError') : eE ? eE[1] < 60 &&

https://static.webinar.ru/new/js/main.bc03b188.js

Analyzing the control flow here & how we arrive at the ProductNotSupportedError outcome:
eT here is truthy (it's an explicit check for firefox in navigator.userAgent, and ei is unset (i.e. they haven't specified unblockUnsupportedBrowsers in the associated configuration here), so we evaluate eu('ProductNotSupportedError') which ends up resulting in us being blocked.

I'm not sure there's anything else that needs diagnosing here, beyond the fact that the site is simply blocking us with UA sniffing.

Comment 2

[Thomas Wisniewski [:twisniewski]]

Today, a UA spoof isn't working for me, but Chrome Mask does seem to work. I'll see what they're trying to check beyond the UA string.

Actually, i think I just botched my initial test, as a normal UA spoof seems to work for me now. I'll try to make a patch for this ASAP.

Comment 3

[Thomas Wisniewski [:twisniewski]]

Attachment: Bug 1898941 - Add UA override for events.webinar.ru; r=ksenia

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/17d3e54e9b12
Add UA override for events.webinar.ru; r=ksenia,webcompat-reviewers

Comment 5

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/17d3e54e9b12

Comment 6

[Dennis Schubert [:denschub]]

Mass-assigning diagnosis-team to webcompat for "Firefox is not supported" bugs that don't already have a team assigned. This action is done by a script. For your convenience, feel free to filter your bugmail with 559a9604-41ec-11f0-9ec6-f3f21dcd7cf2.