Description of the issue: Using BRAVE SEARCH with Firefox. Have had no problems (that I know of) except logging in to my bank’s website. Spent an hour on the phone with support agent from the bank today; he finally decided that the problem was that Brave Search was somehow disguising/hiding my location. I’m not sure I believe him as the login fails even if I type the address into the Firefox address box WITHOUT a search for the website. Is what he says even possible? If it is, can I exempt the bank’s website from any location scrambling that Brave Search does?
Sorry but that bank teller sounds like he just wants to pass the buck off to anyone he can (I honestly didn’t mean the pun as I was writing it… I just wanted to avoid saying he’s full of $#!^, so re-wrote) and in this case Brave Search …
I understand why you would obviously file this under Brave Search but this sounds more like a Browser Support > Web Compatibility issue, which really does NOT sound like it’s a Brave (Search or any other) issue at all, or really anything to do on your end either…
But since you said you were using Firefox with Brave Search, might I ask you to try with Brave Browser (I hear it’s good ) and see if you get a different result?
I certainly wasn’t sure why BRAVE SEARCH would cause such a problem. I’m finding that most banks/CUs don’t make their software compatible with anything but EDGE or CHROME. Even software/hardware companies (Keychron) only support these browsers and I am very reluctant to try an even less-used browser than Firefox.
I appreciate your response. I suspect that it’s a bank compatibility problem.
Neither Brave nor Brave Search would disguise or hide this. You would need to rely on something like a VPN to “disguise” or “hide” the location.
That said, one possibility that I could see argued is different URL. For example, you can visit https://www.amazon.in/ to see Amazon for India or https://www.amazon.de/-/en/ to see Amazon for Germany. So if the URL you clicked on had a domain difference like this, it could result in some differences. But I doubt it would be anything problematic.
Well, 80% of all users are on Chromium based browsers. So due to the vast majority of users on them, these typically get the most attention and compatibility checks. That’s not to mention the vast amount of developers and huge bank accounts funding Chromium projects.
If you haven’t already tried, do make sure to go through some of the more basic troubleshooting steps. For example, to open in a private window to see if it works.
Should an issue happen on that as well, create a new profile and see if it works.
The purpose of these is to test things like cookies, extensions, browser settings, etc. These are typically default things you want to do on any browser when you have issues just to see if they help.
If problems continue even after testing in a new profile or using a private window, it can help to check the site in another browser. To see if the issue is related to the Gecko or Firefox engine, you can try alternatives such as LibreWolf or Mullvad.
You can also test in a Chromium based browser such as Chrome, Brave, or Edge.
If the problem does not appear in other browsers that use the same engine, the issue may be tied to the specific browser you started with. In that case, it is a good idea to let the developers of that browser know. For example, if the issue only occurs in Firefox, you would report it to the Firefox team.
If the problem shows up across multiple browsers that share the same engine, then it may be an engine level issue. In that situation, you can notify the engine developers as well as the website. For example, if the problem appears in both Chrome and Brave, you would report it to the Chromium developers and optionally to the individual browser teams.
) and see if you get a different result?
