We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unknown in UserAgent is causing issues on sites like zoom
navigator.userAgent "Mozilla/5.0 (Unknown; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.30 Safari/537.36"
navigator.userAgent "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36"
Easily
1.16.14 Chromium: 86.0.4240.30 (Official Build) nightly (x86_64)
The text was updated successfully, but these errors were encountered:
Verification PASSED on macOS 10.15.6 x64 using the following build:
macOS 10.15.6 x64
Brave | 1.16.17 Chromium: 86.0.4240.30 (Official Build) nightly (x86_64) -- | -- Revision | 09f50eb5535879364cf00e72653462a509ef6bdc-refs/branch-heads/4240@{#552} OS | macOS Version 10.15.6 (Build 19G73)
Went through the STR/Cases outlined via #11707 (comment) and ensured the correct user agent was being used as per the following:
--> navigator.userAgent "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.30 Safari/537.36"
Also checked http://google.ca/ by searching what is my user agent and ensured the correct UA was being displayed:
what is my user agent
Sorry, something went wrong.
pilgrim-brave
Successfully merging a pull request may close this issue.
Description
Unknown in UserAgent is causing issues on sites like zoom
Steps to Reproduce
Actual result:
Expected result:
Reproduces how often:
Easily
Brave version (brave://version info)
1.16.14 Chromium: 86.0.4240.30 (Official Build) nightly (x86_64)
Version/Channel Information:
Other Additional Information:
The text was updated successfully, but these errors were encountered: