-
Notifications
You must be signed in to change notification settings - Fork 961
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
supportsHistory is broken in Brave Browser #723
Comments
Ah, how thoughtful of Brave to include I'm honestly not sure the best way to fix this. Open to suggestions. In the next major version we won't have this problem because we will only support browsers that support the |
Aside: we should probably also add Brave to our test matrix if BrowserStack supports it. |
why not use feature detection instead of user agent string? |
New features: - Remove legacy browser support (pre pushState) - Add state to hash history - Use custom window when creating history objects - Better history.block API (wip) - Fix location.pathname encoding issues - About 50% smaller - No dependencies Removed features: - Removes basename support - Removes getUserConfirmation - Removes keyLength - Removes hashType - Removes relative pathname support in hash + memory histories Still TBD: - Missing pathname support in push/replace Fixes #624 Fixes #704 Fixes #723 Fixes #726
Heads up: we are no longer doing this check in the v5 beta released this morning. Please give it a shot and LMK how it goes! |
I'm using Brave Browser and hence this userAgent condition is failing
My UA looks like this
Mozilla/5.0 (Linux; U; Android 4.0; en-us; GT-I9300 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
But it does support latest history apis.
Here's the original issue remix-run/react-router#6844
The text was updated successfully, but these errors were encountered: