-
Notifications
You must be signed in to change notification settings - Fork 2.6k
DuckDuckGo + autocomplete suggestions in address bar does not work #17602
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
Comments
@valynor Do you have brave://settings/privacy With that setting you should see the following (I used First few results should match results from DDG.com website: |
@rebron Here's how it looks with DDG: With searx.be it looks like this: Google auto suggestions work fine, too. |
@valynor Did you select DDG from the Default search engine list or from Other Search Engines? I might be wrong, but I'm going to guess you added DDG manually and that might not have registered the autocomplete url that's needed when waiting for DDG to show up on that list or selecting from the default search engine list. Can you try selecting from the Default search engine list? Or deleting the DDG entry you have in brave://settings/searchEngines , go to ddg, and add it back when it shows up. |
Indeed, I added DDG manually. Thanks a lot for your help & time. <3 |
Cool. Closing as fixed. @valynor You can thank me by using Brave Search instead :-) |
When searching from the address bar with DDG I do not get any search suggestions except for old searches from the history and URLs.
Google, Brave Search beta and e.g. searx.be work as expected and do show search suggestions in the address bar.
My query URL for DDG is https://duckduckgo.com/?q=%s
With that exact same query URL I do get DDG search suggestions from address bar searches in both Firefox 91 and Chrome 92 on the same computer.
Brave | 1.28.106 Chromium: 92.0.4515.159 (Official Build) (64-bit)
Revision | 0185b8a19c88c5dfd3e6c0da6686d799e9bc3b52-refs/branch-heads/4515@{#2052}
OS | Linux Mint 19.3
The text was updated successfully, but these errors were encountered: