You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
We have the same problem.
The funny thing is that you recently introduced the Environment API to be able to check the browser compatibility but that API actually needs a CallClient first.
Also having some better docs on the flags of the environment API would also be helpful to determine which flag to best use (once the bug is fixed)
Environment API can be instantiated from CallClient instance, and creation of that one, should not be limited by any os/browser/version combination - once created, you can check if current combination is supported before creating callAgent
let me know if that helps
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
callAgent
is created by client appDesired behavior
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"
The text was updated successfully, but these errors were encountered: