Did you search for similar issues before submitting this one? I browsed the issues labeled autocomplete. #883 is sort of related but there are more issues than just described in that ticket.
Describe the issue you encountered: So, in general, I find brave's autocomplete to be far less useful than Firefox's/Chrome's. This is a bit hard to quantify, but let me describe some concrete problems which I have noticed:
@ezyang Thanks for submitting this request. We are filling in many of the missing history features for our 1.0 launch so this should improve.
We can certainly add at least 2 more entrees for autocomplete matches which will also help solve this issue.
cc @bbondy
I too have this issue... I have a great example which I can share
I will sometimes go to https://google.com/analytics or similar. When I type in google.com, it' auto-completes that entire URL instead of preferring the shorter google.com :frowning:
Also, I know you can delete auto-complete entries, but I don't remember how (it's a keyboard shortcut only, if I remember right)
@alexwykoff The above reports are from Linux so let's confirm this behavior is tri-platform. I think it is.
funny...apparently FX needs some work too:
(typing mens hair and getting mens shoes?)

@bradleyrichter These are search suggestions from your default search engine. It is up to it what it will return as search results so this is no a browser issue.
The bug that I reported for Brave can be clearly seen in the screen cast I have provided. The suggested url is by Brave's autocomplete rather than from the search engine.
Try repeating the same steps as mine under Chrome or FF. Both will suggest the mosy recent or most visited website as highlighted text, but Brave doesn't.
@Sh1d0w not sure why google is giving FX those strange results but chrome and brave are fine with the same steps.
But anyway - your bug above is duly noted and certainly a different issue. We will work on it. Thanks...
Win 7 : 0 results

Ubuntu : 3 results

OS X : 0 results

This does not seem to work for me. I've built it from master https://github.com/brave/browser-laptop/commit/497ecf8679e0bc14ae7d1e05e38f3b5a00733071 and installed it on my system.
I've did the following:
tw in the url barShould I delete all brave related session files in order that to work? It should altomatically work after updating Brave to newest version without requiring any further steps.
Please close if I did something wrong and this report is not valid.
The ordering of the websites is controlled by a count attribute that is stored with each history item. The history items will be ordered by the count (highest first) with some decay based on the last time the website is accessed.
I just tested with a new session file, accessing twilio.com and then twitter.com. Each history item has a count of one.

Twitter is the first entry in the list as it was accessed most recently.
Thanks for the test. Please let us know if you are seeing something different than what I described.
@aekeus I understand this and it is working just perfectly if I remove session-store-1.
The problem is the following:
When we update Brave, the session store file is not removed. It stays as it is, and when you are accessing websites count entry is not created under the visited entry, as it is already in the session file.
To sum it up - everything from your PR is working if I delete session-store-1 file, but you can't expect the users to delete it after the upgrade as they will loose all of their settings and history. The issue is that if you already have session-store-1 file, your PR is not working since the count entry is not appended to the already existing history entries, only to new ones.
For example with the PoC I provided in the comment before yours, when I inspect session-store-1 file the twitter.com entry does not have count property no matter how much times I access this website, because I have visited it before. If I visit webite that I have never visited, it correctly has the count: 0 property.
Sorry for reopening this again or if I haven't explained it well the first time. Let me know if you need more info on this issue.
Hi, Thanks for checking this for us again. I will try and reproduce and fix.
Ok, I can reproduce the issue you are seeing although the root cause is different.
The count attribute is added to existing entries in an existing session file. I confirmed this multiple times by removing the count attribute, opening the browser, navigating to a site, closing the browser and inspecting the session file.
In the specific instance you noticed above the history item have the following locations:
When you enter the characters twi the locations match on the first portion of twitter.com but later in www.twilio.com. twitter.com will always show up first regardless of the number of times you navigate to www.twilio.com.
I am going to close this issue and open another that specifically fixes the prefix issue described above.
Thanks again for looking into this for us.
cc @bbondy