Brave shortcut under search engine section is ALL gone

Description of the issue:
I used to type “g” in address bar and google website will pop up. Now, when i type “g”, it goes to search “g”.

How can this issue be reproduced?

set search engine to “g” to “www.google.com
type g on address bar.

Expected result:

when i type g in address bar, it goes to google website not searching “g”.

Brave Version( check About Brave):

Version 1.76.73 Chromium: 134.0.6998.45 (Official Build) (64-bit)

Additional Information:

After recent update this whole search engine shortcut is messed up.

Typically search shortcuts have a symbol in front of them, so you would type :g rather than just g.

That said, this may be part of a known issue. Can you please share a screenshot of what you see when you go brave://settings/searchEngines?

@tinzi you talking about actually using it to do searches or were you one of the people who were using modified links and trying to cheat the Site Search section to be a bookmark with a custom shortcut to navigate to websites?

If you mean that second part, then just want to point out this is an upstream change through Chromium. You’ll see the same issue on Chrome and all. It’s being looked into and discussed by people at Brave. A user opened a Github for it at https://github.com/brave/brave-browser/issues/44450

But if you’re talking about actually performing searches, then would need to look more at what Mattches is saying.

1 Like

Hello Saoiray/Mattches, I want to go straight to a webisite, i do not want to search anything. Before: key: alt+d (focus web address), then key: a; Amazon shows up. So, Amazon.com= alt+D, A. Now, alt+d, A = google search of “A” which render the whole shortcut usesless.

I can confirm that the linux version of Brave also suffers from the same issue. Brave is still a fast browser and useable, just that it has becoming very inconvenient to user, it doesn’t have to be this way as it was perfectly fine before update. Thanks for looking into it.


Thanks for looking into it, i described this operation in my previous reply.

1 Like

@tinzi yeah. This is a known issue:

I’m going to go ahead and lock this since it’s kind of a duplicate. You can follow up on the Github link I provided earlier or in the topic linked above. Just trying not to have too many topics open on the same issue as it can be distracting.

1 Like