-
Notifications
You must be signed in to change notification settings - Fork 108
Open
Labels
BugSomething isn't workingSomething isn't workingCallingIssue involves Calling functionality.Issue involves Calling functionality.Needs: triage 🔍
Description
I'm currently working on a project that is integrating the Web SDK and I'd like a reliable method for determining browser compatibility. Ideally the web SDK's would provide a compatibility API.
Current Behavior
Use an incompatible browser like Firefox
- User taps on button to join meeting
- User enters name to use during meeting
- User confirms entry
callAgentis created by client app- Fails with unsupported browser exception
Desired behavior
- Client SDK invokes API method
- If browser is compatible
- Perform Join meeting flow
- Else browser is incompatible
- Direct user to meeting alternative
Current Solution
We could use the check that the Hero example uses, treat only Firefox browser as incompatible
However, the documentation describes more than just Firefox being incompatible.
Browsing the analytics reports for our app, about a third of the reported users' browsers are "Unknown"
mychalhackman and davideberlein
Metadata
Metadata
Assignees
Labels
BugSomething isn't workingSomething isn't workingCallingIssue involves Calling functionality.Issue involves Calling functionality.Needs: triage 🔍