-
Notifications
You must be signed in to change notification settings - Fork 500
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
Detect and properly route unsupported browsers. #18
Labels
enhancement
Improves an existing feature
Comments
Closed
I have addressed basic redirection using user agents in 6101706, which is good enough for now. But feature detection is the real goal here, so I am going to leave this issue open. |
There needs to be feature detection to determine which browsers are not supported |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the detection of unsupported browsers is sketchy at best. In the future feature, detection would be the way to go as @joepio suggested.
Maybe this library could help: https://github.com/muaz-khan/DetectRTC
Specific cases that need to be tested: Internet explorer, Older version of Edge, The built-in browsers in mobile apps such as Facebook, Messenger, Twitter, and Snapchat
The text was updated successfully, but these errors were encountered: