-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some errors on Firefox #215
Comments
Is it really necessary to ping 10 people by mentioning a group? It worked fine in FF when we tried it with 4 people this afternoon. So please provide the information of the issue template:
|
That’s what the groups are for. Just to clarify: They were established to get people involved and not only keep the usual people on top of things. (Besides this is not relevant to this issue.) Browser FF 50.1.0 This is the log exactly as it appears in the screenshots
Steps to reproduce: As said above, use our cloud.nc instance and open the Spreed app. |
This works pretty fine for me with Firefox 50.1.0 on Linux Mint (Ubuntu 16.04 based). |
Please also open your JS console and run the following two commands:
|
Aaah, thanks a lot! I was actually using an extension »User Agent Overrider« which I totally forgot about! It overrode the user agent with:
(It’s a commonly used hack needed to make Netflix work with Firefox.) Any way to have the app not stumble over it? Talky.io for example had no issues with it, that’s why I thought it to be an issue on our end. |
Okay I get the same error with that user agent. Will try to find the issue. |
Well that's obvious now, the webrtc lib detect Firefox by checking whether Easy fix, add the actual Firefox version back into the user agent. |
Seems it was broken on Firefox recently? cc @nextcloud/spreed any idea?
That was on our cloud.nc instance just now.
The text was updated successfully, but these errors were encountered: