this post was submitted on 20 Oct 2024
143 points (95.0% liked)
Firefox
20466 readers
3 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What is your config? It's possible you've got things configured in an unexpected, but valid, way that causes Google Meet to fail.
How does it fail? Are there errors in the console?
You're immediately assuming malice, but it may simply be a mistake (Google's or yours).
I am pretty sure no one at Google tests outside Blink & only gets around to it when there are bug reports
Part 1
So first off I appreciate your "about:config" dump, that is helpful.
However, having ONLY that dump makes it difficult to actually diagnose your issue. It would be helpful to have an idea of what fails.
Second, you have "media.peerconnection.enabled" set to "false". That setting controls WebRTC. Google Meet uses WebRTC. If I set that value to false my Google Meet meetings fail to load, it just stays stuck at the joining meeting phase.
So maybe that's your culprit. Of course I would expect if you've had this set for a long time I would have expected it to fail for a long time. Also both alternatives you mentioned use WebRTC, so I would expect those to fail with that setting disabled.
Of course if it used to work with that disabled then it's possible Google Meet changed and had a fallback no longer in use or something else.
As an aside, I understand that WebRTC has (had?) issues leaking local IP addresses while connected to a VPN. So I understand why you might have it disabled.
The webrtc setting is probably it. IMO it's still google's fault for not providing a meaningful error message. It just stuck on the loading screen, assuring me that I would enter the meeting but I just didn't. I don't like webrtc because it can be used for fingerprinting, so I will probably use jami in the future. Thank you very much for diagnosing my problem!
Part 2
Great. Your job is to take standard Firefox and switch one of these settings on at a time, testing Google meet until you find which one is the culprit. Good luck! 👍