Firefox support about jitsi-meet HOT 73 CLOSED

I was just about to enter the same issue ;).

Firefox support would also require a few additions in Jitsi Videobridge. It's something we'd like to do as well.

Other browsers would need to first add support for WebRTC or ORTC

from jitsi-meet.

Are you have any idea, when we can expect that support (for FF)? I mean even some approximation - be it a month or two, or more? :)
I think it is quite important for many of us :)

from jitsi-meet.

It really depends. It will probably take a month or so to get everything ready but right now we don't really know exactly when we'd be able to start.

from jitsi-meet.

I suppose we will be able to beat Firefox at https://bugzilla.mozilla.org/show_bug.cgi?id=784517

from jitsi-meet.

This is going to be relatively complex and we better address stability and scalability issues first. Hopefully, at some point, Firefox would stand up and implement at least a part of what they are advising everyone else to do.

from jitsi-meet.

At least recommend Chromium, not Google Chrome.

from jitsi-meet.

@andreicristianpetcu , Chromium is already supported.

from jitsi-meet.

emcho: https://meet.jit.si/chromeonly.html might alternatively recommend chromium indeed. Or Opera :-)

from jitsi-meet.

It's strange that the only browser that jitmeet supports and promotes is a proprietary browser. I assume Jitmeet is as privacy oriented as Jitsi. Google Chrome and Opera are on the "dark side" of privacy :)

from jitsi-meet.

@andreicristianpetcu That's pretty true. At least Chromium should be recommended, but better support Firefox and others under GPL & Co.

from jitsi-meet.

@mokkin Firefox simply does not support receiving multiple streams in a single peer connection and working around that problem is neither trivial nor efficient or in other words: an ugly, clumsy hack.

For the record: last summer, following intense debates at the IETF, Firefox have deliberately chosen not to follow our advice on the most straightforward and simple, yet flexible way of implementing multi-stream support.

They have instead decided (and convinced a number of people) to go down a path that is much more convenient for legacy VoIP companies like Cisco (that also happen to be funding Firefox's work on WebRTC). They have chosen to do this in spite of a number of comments cautioning them against the (perfectly unnecessary) extra complexity of their plan.

Anyways, that hatchet would have been long buried had they only followed through.

Today however, every time someone dares ask about multi stream support, they keep explaining how implementing it is "oh so complicated" and that there are workarounds anyway. Back to square 1.

from jitsi-meet.

Step 1: Promote Chromium as well as Google Chrome until Firefox as a good WebRTC implementation :)

Step 2: convince Firefox to do the proper implementation by following this bug https://bugzilla.mozilla.org/show_bug.cgi?id=784517
I already subscribed to the bug. Hope other people on this issue will do the same. Maybe with enough presure, we can get it implemented.

from jitsi-meet.

@andreicristianpetcu Sounds like a plan! Looking forward to your step 1 patch!

from jitsi-meet.

back to tech details of getting firefox to work... one of the disadvantages of the plan outlined in https://hacks.mozilla.org/2013/09/webrtc-update-and-workarounds/ is that we would have to either have multiple peerconnections for chrome also (which is a no-go).
Or we would need the SSRCs firefox sends to allow chrome to do demultiplexing. I don't think firefox announces them already, but the bridge can tell the focus about the SSRCs it receives.

I'll probably split out audio-only firefox support from this ticket.

from jitsi-meet.

@fippo Yes, that's what I meant by non-trivial. We'd basically need Jitsi Videobridge to allocate SSRCs and then overwrite them for every stream. We'd also need peer connection SSRC filtering and we'd have a hard time adding and removing channels and signalling them and running ICE and DTLS/SRTP for every new peer connection ... it's a mess.

from jitsi-meet.

+1

from jitsi-meet.

Would it at least be possible to have one-to-one support for Firefox users?

from jitsi-meet.

1-1 via the bridge works (see issue #46), but using a server in the middle has little advantage for that usecase.

from jitsi-meet.

I see people are working on Firefox support in the following branch: https://github.com/jitsi/jitsi-meet/commits/firefox
Which is really awesome! Are there any updates on this?

from jitsi-meet.

Yes, the Firefox team have started working on multistream support. The branch is in preparation of that, but we first need ms support to land in ff.

from jitsi-meet.

Thanks for the update!
I really appreciate the work you guys are doing.

from jitsi-meet.

Cool stuff! Thank you! You guys are really cool!

from jitsi-meet.

https://bugzilla.mozilla.org/show_bug.cgi?id=784517 has been resolved as a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1095218 - and the later has been resolved as fixed last Thursday. Unfortunately, the code in question uses browser detection rather than feature detection, so the current Firefox nightlies will still redirect to chromeonly.html. If I change config.enableFirefoxSupport setting in debugger things seem to work correctly (except for audio).

from jitsi-meet.

Hey @palant . Support in Meet is still being worked on and the corresponding support in firefox is still being stabilised. We will obviously change the browser check once we actually support another browser

from jitsi-meet.

I see that commit 05bbfda now adds support for firefox multistream. Is it for FF 38 Aurora/DevEd?

from jitsi-meet.

Was FF support added in release 2.8? Thank you!

from jitsi-meet.

@TabeebOsama the recent 2.8 release was of Jitsi (the desktop client), not Jitsi Meet. Firefox support was recently added to Jitsi Meet, but AFAIK it is still experimental.

from jitsi-meet.

As @bgrozev says, FF support is still experimental but it is enabled by default for Firefox Nightly users.

from jitsi-meet.

Thank you for your prompt replies. I know this is not this thread. However, I have two more questions related:
1- Which IE plaug-n does Jitsi support and you recommend?
2- Will you support Bowser?

Thanks,

from jitsi-meet.

@TabeebOsama please send your question to the mailing list.

from jitsi-meet.

any workarround?

can't we merge audio+video streams into one stream..? will it work if enableFirefoxSupport=true

from jitsi-meet.

@dev-mraj any workaround for what exactly?

from jitsi-meet.

Firefox support (current stable version)

from jitsi-meet.

adding "enableFirefoxSupport: true" in config.js should work.

from jitsi-meet.

Is this for nightly Firefox or all Firefox?

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message

On Mar 30, 2015, at 13:25, gpolitis [email protected] wrote:

adding "enableFirefoxSupport: true" in config.js should work.

—
Reply to this email directly or view it on GitHub.

from jitsi-meet.

Firefox support only works for Firefox Nightly (v39), at least for now. We might enable it for Aurora/Dev edition (v38) as well but it's not going to work with stable (v37).

from jitsi-meet.

whats the status of "We might enable it for Aurora/Dev edition (v38)"?

from jitsi-meet.

It is actually enabled for v38 (now beta). We're still blocked by this though.

from jitsi-meet.

FF v40 (now Aurora) includes some important fixes and it seems to be working relatively well with meet, if people want to test.

from jitsi-meet.

George, what's up with https://bugzilla.mozilla.org/show_bug.cgi?id=1155246 ? Is it still a valid bug? Your last comment seems to indicate otherwise.

Also using 40.0a2 (2015-05-27) when I click the icon with the person and the plus sign, it says "Your link is being created" to share the link with another person, but it never finishes.

from jitsi-meet.

My last comment still applies. I'm not sure if it's gone (or if it ever existed), but it doesn't seem to affect meet anymore.

from jitsi-meet.

Thank for trying this out! I'm not able to reproduce this on https://beta.meet.jit.si/. Could you please paste the JS console log here?

from jitsi-meet.

Sent to you via encrypted mail.

from jitsi-meet.

As per our private conversation, the problem appears to be that you try to enter the conference without sharing your camera. I've noted this in #271. Also, screen sharing doesn't currently work. That's documented in #296.

from jitsi-meet.

Means this, that it will work with 40 (Aurora)

https://hacks.mozilla.org/2015/06/firefox-multistream-and-renegotiation-for-jitsi-videobridge

from jitsi-meet.

This does now work with the now full-release FF 40. This should probably be closed, but FF isn't fully on-par until #296 is done (and maybe some other items)

from jitsi-meet.

Is there any chance that this will work on Firefox for android? Currently it shows the not-supported screen after typing in a room name.

from jitsi-meet.

@geileszeuch are you on FF 40 ? ( I don't know if that works, but I know it won't work if on older)

from jitsi-meet.

I am FF 40.

from jitsi-meet.

@geileszeuch Unfortunately I don't think FF for Android has support for WebRTC, so we can't support it even if we wanted to. OTOH the performance would be absolutely abysmal, unless it runs on powerful hardware; so my thinking is that native is the way to go for mobile devices.

from jitsi-meet.

I am sorry, I had my user agent edited. It works totally fine on Android and the performance is also quite good on my phone. Thank you guys. Its time to say goodbye to Skype.

from jitsi-meet.

@geileszeuch great to know! I should try that myself

from jitsi-meet.

This is unexpectedly good news, thanks @geileszeuch for sharing your experience with us. Could you please share what tablet/smartphone you're running meet on?

from jitsi-meet.

This will be an important feature to add.

Thank you,
Osama

On Aug 14, 2015, at 5:35 PM, Aaron Wolf [email protected] wrote:

This does now work with FF 40. This should probably be closed, but FF isn't fully on-par until #296 #296 is done (and maybe some other items)

—
Reply to this email directly or view it on GitHub #4 (comment).

from jitsi-meet.

I just tested audio / videoconference at https://meet.jit.si/ using
1- Galaxy Note 3 with Firefox 40 installed with F-Droid
2- Firefox 40.0.2 on Windows 8

It all seems to work fine. Congrats! This is very very exciting!

Jitsi Meet is not responsive though. I brought this up on the dev mailing list:
http://lists.jitsi.org/pipermail/dev/2015-August/025018.html

Thanks!

from jitsi-meet.

I used an Nexus 5. The user interface is a little tiny, but I am happy it works.
And just a side note, I used F-Droids Fennec 40.0 build.

from jitsi-meet.

Hi!

So general Firefox support is resolved AFAICT.

I added a PR to add Firefox to supported browsers page:
#354

I realize some issues are being discovered such as:
#343
But these should be treated as browser-specific bugs (each with their own bug report), just like if they affected another browser.

Thanks!

from jitsi-meet.

Agree w @marclaporte. Why is this still open?
If prio 1 is highest tag prio:7 seems rather low for support of the second most used browser worldwide.

from jitsi-meet.

Thank you for the reminder.

from jitsi-meet.

AFAIU if you close this issue, it should mean that I can access http://meet.jitsi.org/ with my Firefox browser. But I can't. The version I'm using is 41.0 (in Ubuntu 14.04.1).

from jitsi-meet.

Can you access https://meet.jit.si/ with FF? I'm not sure what version of meet we're running on https://meet.jit.si/, probably an older one.

from jitsi-meet.

Can you access https://meet.jit.si/ with FF?

Yes that seems to work.

I'm not sure what version of meet we're running on https://meet.jit.si/, probably an older one.

Can you upgrade it or make it to rather redirect to https://meet.jit.si/?

from jitsi-meet.

Good to hear that it works for you and I'm sorry for the confusion! I'll try to find out what the situation is with m.j.o.

from jitsi-meet.

Hey,
so Firefox is supported now? Does not work for me with 43.0.4 of Firefox.
What are the supported browsers right now?
Thanks!

from jitsi-meet.

I agree the ticket situation is confusing. This was closed when #45 was created. Then #45 was closed referring that FF issues are now tracked in #4 (despite #4 already being closed). That logical issues aside, in my tests, Firefox (which you should update to v44 since that has 9 security fixes you should want on your system) works fine using meet.jit.si.

from jitsi-meet.

@KuenzelIT feel free to drop us an email if you're experiencing problems with FF. As @foss- is saying, it should be working fine right now.

from jitsi-meet.

Still does not work, this is how it looks for me:
http://s10.postimg.org/ybbv4zhq1/Meet_Jitsi_FF.png

Can't really do anything there. It works in IE 11.

Maybe it is something with my FF specifically, there are some rare sites, where nothing seems to work. Maybe I'm going to try it without add-ons...

from jitsi-meet.

Still does not work, this is how it looks for me:

Open up the java scropt console and look for errors.

from jitsi-meet.

These are the errors in the console:

This appears to be Firefox, ver: 44 lib-jitsi-meet.min.js:3:27489

ReferenceError: mozRTCSessionDescription is not defined lib-jitsi-meet.min.js:4:29512

mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create app.bundle.min.js:11:11895

ReferenceError: JitsiMeetJS is not defined app.bundle.min.js:7:24492

Does this help? I don't have a clue what's wrong there.

from jitsi-meet.

Thank you @KuenzelIT. Have you by any chance disabled WebRTC in Firefox?

from jitsi-meet.

For reference, the relevant about:config preference is called media.peerconnection.enabled. It cannot be changed via Firefox settings but this add-on will change it for example. With media.peerconnection.enabled set to false the mozRTCSessionDescription constructor will indeed be undefined.

from jitsi-meet.

Looks like it was disabled. media.peerconnection.enabled was set to false, altough i don't remember changing it. I could change it without an add-on

Thanks for your help!

from jitsi-meet.

You're welcome @KuenzelIT. I'm locking this conversation because any bugs in our FF support should be entered as new issues and questions about our FF support should be addressed in our mailing list.

from jitsi-meet.