100% support for Firefox (and other non-Chrome browsers)

jans23 commented 5 years ago

I'm using Jitsi Meet (The public service hosted at https://meet.jit.si/) for two years now and in my experience it doesn't work reliably with Firefox. I even think as soon as one of the conference members uses Firefox, sooner or later the conference will experience some audio or video issues. Consequently we can't use Jitsi Meet well for a wider/external audience because we can't demand them to use Chrome.

The actual issues experienced range from voice and video drop outs, to connectivity issues (poor connectivity or connection lost). As soon as the Firefox members leaves, the issues stop appearing. Because these issues are so blur I can't provide any details at the moment. Therefore I have the general question, if you plan to support Firefox 100%? If I should provide more technical details about the issues, where can I find description how to gather those details?

johanricher commented 4 years ago

FYI Brave is based on Chromium.

Pascal-KOTTE commented 4 years ago

And it's also FOSS and very privacy friendly. Shouldn't we add it to the supported - and maybe even recommended - supported browsers?

https://en.wikipedia.org/wiki/Chromium_(web_browser)#Browsers_based_on_Chromium And about near 100% base browser any Androïd

Well the new EDGE also very well supported! https://www.microsoft.com/fr-fr/edge/ oops...

steve-clickacall commented 4 years ago

thanks for the youtube clip Peter. But from a user perspective, what can they expect to see differently? and is there anything that will still not work well on firefox/safari?

jallamsetty1 commented 4 years ago

thanks for the youtube clip Peter. But from a user perspective, what can they expect to see differently? and is there anything that will still not work well on firefox/safari?

Improvements to signaling

Better handling of how remote sources are added and removed on the client. All the issues where audio/video is not received when a Firefox/Safari participant joins the call should be fixed.

Improvements to bandwidth estimation and adaptation

By adding simulcast support to Firefox and Safari, we are now able to adapt to the changing network conditions on the downlink. The bridge will be able to send 180/360/720 stream based on the available downlink as opposed to sending 720p always.
Enhancements to our bandwidth probing mechanisms for both Safari and Firefox resulting in more accurate bandwidth estimates.

New Features

Desktop sharing support added on Safari.

Statistics

Fixed transport stats for Firefox and Safari.

eliot-akira commented 4 years ago

Thank you for the update, @jallamsetty1 - I'm sure many in the community will welcome these improvements to support non-Chrome browsers. If there will be a blog post (even a short one), we'll be happy to promote it.

steve-clickacall commented 4 years ago

Thank you @jallamsetty1 this sounds like some amazing work that will help the entire community. We are still deciding whether to switch our product from tokbox to jitsi. I am 100% sure it is a good move, but my non-tech business partner is unsure because of non-support for these browsers. So can you just confirm, in a non-tech way, that safari and firefox will now be “fully working”? And for safari, does this include all mac, iphone and ipad devices?

chagai95 commented 4 years ago

for safari, does this include all mac, iphone and ipad devices?

I'm pretty sure it does - there is an iPhone app which is more stable and has priority if I understood correctly and the safari iPad and Mac is the same safari I was told. I assume safari on iPhone will not be supported for a while but safari for desktop (which is the one on iPad too) will hopefully work in the next few weeks.

kr4ut commented 4 years ago

@jallamsetty1 Wonderful news :heart_decoration: Can we assume it will obsolete the resolution option? We're currently using that countries/groups with low bandwidth. Any plan when your awesome work will hit Debian stable packages?

DBJRdev commented 4 years ago

@kr4ut : Don't know whether it helps, but at least it's easy to check visually for new package releases via browser: https://download.jitsi.org/stable/ In the community call they said probably within the next 1-2 weeks (counted from today)

freechelmi commented 4 years ago

AFAIK , Safari does not have any capture audio support yet.

steve-clickacall commented 4 years ago

@chagai95 - oh, so jitsi meet will still not work on iPhone safari browser? ;-(

chagai95 commented 4 years ago

@chagai95 - oh, so jitsi meet will still not work on iPhone safari browser? ;-(

I have no idea, I believe it won't - let's see in two weeks :) I would also try clicking on desktop mode maybe that'll do the trick and I think it doesn't work on Chrome on iPhone either...

kr4ut commented 4 years ago

@DBJRdev Thanks for telling the road map just looking at packages releases doesn't help :wink: @jallamsetty1 Beside all the doesn't work for me locally reports here we just reconfirmed a simple test case between two Firefox 75.0 (Ubuntu 18.04 build) via v2.0.4384-1 and comparing desktop bandwidth with nload. Iterating resolution at server config with 720/480/360/180 doesn't make any difference. Neither does changing video quality client wise in Firefox. Bandwidth starts shortly around ~0,8Mbit and goes directly to constant ~3Mbit. Only low bandwidth and disabling video brings it down to ~80Kbit.

freechelmi commented 4 years ago

@chagai95 - oh, so jitsi meet will still not work on iPhone safari browser? ;-(

I have no idea, I believe it won't - let's see in two weeks :) I would also try clicking on desktop mode maybe that'll do the trick and I think it doesn't work on Chrome on iPhone either...

You'll have to disable deep linking in config.js first.

chagai95 commented 4 years ago

@chagai95 - oh, so jitsi meet will still not work on iPhone safari browser? ;-(

I have no idea, I believe it won't - let's see in two weeks :) I would also try clicking on desktop mode maybe that'll do the trick and I think it doesn't work on Chrome on iPhone either...

You'll have to disable deep linking in config.js first.

On Chrome clicking on desktop mode is sometimes enough otherwise you could open from incognito with desktop mode active and that always worked for me - maybe it's the same on safari?

FlorianLudwig commented 4 years ago

Hey all,

I get a lot of notifications here for ... something that is now a chat and not updates to the actual issue.

I believe there are more of people like me - subscribed here to this issue because it is an important one for them. Please keep this in mind when posting here! And move (general) discussions some place more appropriate.

Please? Thanks :heart:

steve-clickacall commented 4 years ago

apologies @FlorianLudwig some of us are new so not sure of the rules.

@everyone lets go to https://community.jitsi.org/t/browser-support-warning-when-using-the-latest-firefox-71-0-version-on-meet-jit-si/21180 to continue this discussion about improvements to firefox/safari support away from here (which is best left for the amazing dev team to do the actual changes ;-)

See you all at https://community.jitsi.org/t/browser-support-warning-when-using-the-latest-firefox-71-0-version-on-meet-jit-si/21180 so we can continue discussing this at a "user level" ;-)

keithwbacon commented 4 years ago

I was going to post about being unable to use Safari 13.1 on OS X 10.15.4 but I noticed if I change the user agent to Google Chrome MacOS it worked "good enough" for my purposes. I'm using the current stable release of Jitsi-meet. 2.0.4384-1. Thanks!

mohicanb commented 4 years ago

Hello, are the other Blink-based browsers like Brave https://brave.com/ and Falkon https://www.falkon.org/ 100% compatible with Jitsi Meet ? If so please add them to the recommanded browsers list.

ulab commented 4 years ago

Brave is Chromium based and works here. No warning or anything, so I don't think it needs to be added to the recommended browsers list? Just as the 20+ other browsers based on Chromium either. Otherwise the list is going to get really long.

Falcon is based on the QtWebEngine. I am not sure if it will work and can't test it.

chagai95 commented 4 years ago

Brave is Chromium based and works here

Is Brave on Android also Chromium-based? I couldn't find an answer online...thanks for your answer!

ulab commented 4 years ago

Is Brave on Android also Chromium-based? I couldn't find an answer online...thanks for your answer!

It is, but Jitsi still tells you to use the app.

astrojuanlu commented 4 years ago

Hey all,

I get a lot of notifications here for ... something that is now a chat and not updates to the actual issue.

I believe there are more of people like me - subscribed here to this issue because it is an important one for them. Please keep this in mind when posting here! And move (general) discussions some place more appropriate.

Please? Thanks ❤️

abitrolly commented 4 years ago

Firefox RTX for WebRTC is getting some commits - https://bugzilla.mozilla.org/show_bug.cgi?id=1164187#c53 )

HelloWorldUser123 commented 4 years ago

Hi, just for clarification - the fixes for Firefox and Safari, are these related to Jitsi or directly to Firefox. My question, do I have to update Firefox or are older versions i.e. Firefox ESR 68 also supported? Thanks

jens1o commented 4 years ago

@HelloWorldUser123 The fixes included in Firefox will not be backported to the 68 ESR version. The next ESR version is scheduled to release in end June/early July.

Proof (while actually it is from me): https://twitter.com/firefox/status/1246398994928087048

HelloWorldUser123 commented 4 years ago

Thanks for the answer. But regarding this issue says 100% support for non-Chrome browsers means for me also safari. Are there also changes coming directly to Jitsi to better support Firefox and Safari at all? We are currently seeing with multiple attendees of firefox a lot of errors "addRemoteStream" where the picture freezes and so on.

jallamsetty1 commented 4 years ago

Thanks for the answer. But regarding this issue says 100% support for non-Chrome browsers means for me also safari. Are there also changes coming directly to Jitsi to better support Firefox and Safari at all? We are currently seeing with multiple attendees of firefox a lot of errors "addRemoteStream" where the picture freezes and so on.

Hey there, yes the changes to Jitsi will include fixes for Safari as well. Do you have the latest lib-jitsi-meet or jitsi-meet (depending on your implementation) ? We had a meet.jit.si release last weekend which should include fixes for addRemoteStream issues. If you still see errors, can you please send me the logs ? Thanks !

steve-clickacall commented 4 years ago

But will this include Safari on iOS?

jallamsetty1 commented 4 years ago

But will this include Safari on iOS?

We are working on fixing video rendering issue on Safari on iOS. Currently, media is sent and received by the client but only the first frame is rendered.

HelloWorldUser123 commented 4 years ago

Hey, thanks for the fast answer. Actually we are still on the version before the weekend. That are great news. Tomorrow we will try it with the new version - I will update you if the issues are again.

But will this include Safari on iOS?

We are working on fixing video rendering issue on Safari on iOS. Currently, media is sent and received by the client but only the first frame is rendered.

We experienced this issue in iOS safari for video elements which doesn't have the playsinline attribute in place. I don't think that the problem is that only the first frame is rendered. I think the problem is that iOS safari doesn't autoplay it. Please try to add the "playsinline" attribute to the video tag. https://developer.apple.com/documentation/webkit/safari_tools_and_features/delivering_video_content_for_safari

jallamsetty1 commented 4 years ago

Hey, thanks for the fast answer. Actually we are still on the version before the weekend. That are great news. Tomorrow we will try it with the new version - I will update you if the issues are again.

But will this include Safari on iOS?

We are working on fixing video rendering issue on Safari on iOS. Currently, media is sent and received by the client but only the first frame is rendered.

We experienced this issue in iOS safari for video elements which doesn't have the playsinline attribute in place. I don't think that the problem is that only the first frame is rendered. I think the problem is that iOS safari doesn't autoplay it. Please try to add the "playsinline" attribute to the video tag. https://developer.apple.com/documentation/webkit/safari_tools_and_features/delivering_video_content_for_safari

This is very helpful, will give it a try, thanks !

steve-clickacall commented 4 years ago

@jallamsetty1 and @HelloWorldUser123 thank you for the update. We have had similar issues with Safari on iOS. Mobile browsers is key for us, so please let us know if you need help with some extra testing...

cpot commented 4 years ago

Perhaps a specific issue for Safari will make sense (Chromium should not be an issue, it works well with Edge-Chromium and Opera as far as we know)

This issue is too broad unless everything can be solve at the same time (is it realistic?)

Thank for all team working hard to make Firefox (and next ESR) working with jitsi, we see a big demand

HelloWorldUser123 commented 4 years ago

But will this include Safari on iOS?

We are working on fixing video rendering issue on Safari on iOS. Currently, media is sent and received by the client but only the first frame is rendered.

We tested it with iOS safari and your change yesterday, thanks for that. Video is working as viewer. But now iOS has some problems when someone joins or someone (also myself) switch the camera - it runs into an error and reloads. edit: only if there are two or more people in the room

Dan33l commented 4 years ago

For placing the church in the center of village, the jitsi sdp-interop gives corrects details of troubles with Chrome-like browsers and all the rest of the world.

bhack commented 4 years ago

@Dan33l In what transition phase we are now with current stable chrome and derivatives? https://webrtc.org/getting-started/unified-plan-transition-guide

bhack commented 4 years ago

The most updated info is that I find is at https://bugs.chromium.org/p/chromium/issues/detail?id=857004

pdarcos commented 4 years ago

Just updated my installation to latest unstable and tried using Firefox (75.0 64bits) on ubuntu.

It seems to work mostly well except I noticed that 1) P2P and bandwidth stats are still buggy/empty 2) Firefox doesn't offer me any options for choosing speakers, just camera and microphone. The speakers drop down is empty, but I know it can see my USB headset since the microphone shows up on the dropdown list as expected. 3) Tried using the exact same setup with Chrome and there the headset speaker is present and the P2P/bandwidth stats work fine.

Hope this helps. Thanks for the great work. Can't wait to have full Firefox support working well with Jitsi-Meet!

jallamsetty1 commented 4 years ago

Thanks for testing out the latest unstable, it is appreciated! We are in the process of making a release this week with all these changes. Let's not spam this thread with browser specific issues, please start a new thread once the release is out. From Jitsi side of things, all the work for getting the signaling and media to work correctly on non-chromium browsers is done. The issues that have been reported above with device detection and stats are browser limitations/bugs. For example, Firefox and Safari don't let us set the sink for audio, i.e., change the audio output, it has to be done through the system settings only. There are more of these browser specific limitations, I will be happy to give links to the corresponding browser bugs in the browser specific thread. The only exception is P2P, we have disabled it for non-chromium based browsers because we are running into BWE issues, we will turn it back on once those issues are sorted out.

saghul commented 4 years ago

I'm closing this since we have the first step in place. Please open new issuess speccific to a given browser, should you find any.

bhack commented 4 years ago

@saghub Let us know if you have a list of upstream bugs in Firefox's bugzilla the we can upvote.

leonardehrenfried commented 4 years ago

As posted upthread, here is a list of bugs with the tag jitsi-meet: https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&status_whiteboard=jitsi-meet

I can't say how relevant these bugs really are. At least on of them is actively worked on.

cpot commented 4 years ago

This Firefox compatibility is a huge improvement for Jitsi, thank you a lot.

When the .deb release will be ready? (we hope very fast)

damencho commented 4 years ago

This is already available in latest debian packages in unstable repo.

bhack commented 4 years ago

You can also use the last Firefox stable from https://flathub.org/apps/details/org.mozilla.firefox

cpot commented 4 years ago

This is already available in latest debian packages in unstable repo.

Thank you very much.

How it is possible to know which version we are using on https://meet.jit.si/ i can't find a way to know the build number
Do you have a expected date for stable repo ?

Again thank you

damencho commented 4 years ago

Do you have a expected date for stable repo ?

And we just pushed a stable with the latest changes.

How it is possible to know which version we are using on https://meet.jit.si/ i can't find a way to know the build number

That is a tricky one :) So we normally try to push a version that matches the jitsi-meet version (the meta packages), but it is not always possible, like today :) Stable jitsi-meet now is 2.0.4468.

So to check the versions on meet.jit.si, open the HTML sources and you will see: base href="https://web-cdn.jitsi.net/meetjitsi_4025.677/ From here you can get the web version 4025 is what is now in stable. Then open two tabs and open Developer Console and filter by version and you will see jicofo and jvb version:

tpo commented 4 years ago

@damencho I'd be glad if you could clarify: which of the following statements is true?

the latest stable Jitsi Meet release (as released as Debian packages) contains improvements that make it work just fine with current Firefox ESR
the current nightly build of Firefox works just fine with the latest Jitsi Meet release

From reading the comments above I can not figure out which one of these statements is true. By "working just fine" I mean "does not disrupt the experience for all other participants due to missing RTX implementation".

?

Thanks a lot!

damencho commented 4 years ago

the latest stable Jitsi Meet release (as released as Debian packages) contains improvements that make it work just fine with current Firefox ESR

Nope, we just disabled simulcast for ESR. I think the next ESR coming in two months will be fine.

the current nightly build of Firefox works just fine with the latest Jitsi Meet release

Yes.

jitsi / jitsi-meet

100% support for Firefox (and other non-Chrome browsers) #4758