search

jitsi / jitsi-meet

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
https://jitsi.org/meet
Apache License 2.0
22.88k stars 6.69k forks source link

Jitsi Meet "not working" with Icecat #4836

Closed Perflyst closed 4 years ago

Perflyst commented 4 years ago

Description

Icecat is the GNU version of firefox. Looks like Jitsi Meet doesnt like it.

Current behavior

For example https://meet.jit.si/ displays that the browser is not supported

Expected Behavior

Jitsi meet should just work, Icecat is normal Firefox with some things removed for better privacy.

Possible Solution

Add Icecat useragent (?) to supported list

Steps to reproduce

  1. Install Icecat
  2. Open https://meet.jit.si/
bgrozev commented 4 years ago

Can you please post the UserAgent string and the logs from the javascript console? You can filter for just "BrowserCapabilities" in the console.

Perflyst commented 4 years ago

Old LTS Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 or new LTS Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0 (it is using privacy.resistFingerprinting: true)

From console 2019-11-16T15:50:19.200Z [modules/browser/BrowserCapabilities.js] This appears to be unknown, ver: undefined

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Ambrevar commented 3 years ago

Can we reopen this issue? More generally, Jitsi should test for capabilities, not User Agents. I suspect that any browser that has WebRTC support but not the known user agent won't work on Jitsi, while it should.

Workaround for IceCat users: Install the https://addons.mozilla.org/en-US/firefox/addon/uaswitcher/ extension and switch to the Firefox user agent.

saghul commented 3 years ago

Unfortunately that doesn't quite work in practice. Some things can't be checked at runtime.

Ambrevar commented 3 years ago

That's OK! :)

Preventing access to select user agents is not a good option: it's better to just display a warning and let the user proceed at their own risk.

saghul commented 3 years ago

Preventing access to select user agents is not a good option: it's better to just display a warning and let the user proceed at their own risk.

I beg to differ: they may have a bad experience because the software is not tested on their browser, and they'll think it's the software which doesn't work. There are some Chromium builds our there which remove WebRTC altogether, for example. I have no idea what changes IceCat has.

Ambrevar commented 3 years ago

Isn't displaying a warning banner enough?

Also consider that restricting Jitsi to Firefox and Chrome may be further entrenching the dominance of an already rather monopolized market :/

saghul commented 3 years ago

Isn't displaying a warning banner enough?

It has proven to not be the case.

Also consider that restricting Jitsi to Firefox and Chrome may be further entrenching the dominance of an already rather monopolized market :/

It's not explicitly restricted. WebRTC support in browsers has a painful history. If you / we know it works, feel free to open a PR so we treat IceCat as Firefox, that should do it.

Ambrevar commented 3 years ago

IceCat has the exact same WebRTC support as Firefox. Accepting IceCat user agent would fix it.

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Ambrevar commented 3 years ago

Thanks in advance :)