-
Notifications
You must be signed in to change notification settings - Fork 61
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
Firefox support in CallComposite #3796
Comments
Thanks for opening this issue! Looking at our repo code, looks like we are doing some permission query in the file packages/react-composites/src/composites/CallComposite/utils/Utils.ts Will open a bug and doing follow up investigation of fixing this! |
Hi @Mrlten as of right now firefox is only in public preview for the azure/communication-calling package and the UI library. As a result there will be some hiccups with the two SDK's. In the mean time until we fully support our calling experiences on the browser we recommend using another browser like Chrome, Edge or Safari depending on your platform. Please see our browser support docs here: https://learn.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/calling-sdk-features |
Internally we have filed work to update the UI library to fully support Firefox but as of today it is unsupported. |
@JamesBurnside If this is going to be fixed, maybe we could leave this issue open? As it's a useful way for us to track when firefox support will be supported - because it not 'completed' nor is it a won't fix. Firefox support is important to our customers. |
We have the same issue. any timeline for it? |
I'm not sure whether this should be considered a bug or a feature request.
Describe the bug; what happened?
Starting the CallComposite preview in Firefox results in no cameras found and the following errors in the browser console:
According to the Azure Communication Services documentation the SDK should support Firefox, but what about the UI library?
What are the steps to reproduce the issue?
What behavior did you expect?
I would expect Firefox to be supported by the UI library.
If applicable, provide screenshots:
In what environment did you see the issue?
The Storybook demo/preview site. According to a log line in the console:
This Storybook was compiled for @azure/communication-react version 1.10.0-beta.1
The text was updated successfully, but these errors were encountered: