-
Notifications
You must be signed in to change notification settings - Fork 973
Autocomplete does not work well #3049
Comments
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 😦 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. |
@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... |
…ount * Re-order results to show history items before bookmark items * Record number of times site is visited * Re-order history items based on number of times visited and last access timestamp * Update and create tests Fixes: #3049 Auditors: @bbondy Test plan: A new attribute, count, is added to history items in the sites section of save-session-1. This attribute records the number of times a site has been accessed. The test plan is broken in two components, one to verify the count attribute is incremented on access, the second to verify that the count and last access time are used when sorting history suggestions. Scenario 1 Part A 1. Clear save-session-1 2. Access a site 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has a value of 1 Part B 1. Open browser 2. Navigate to site from Part A 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has an incremented value Scenario 2 1. Clear save-session-1 2. Open browser 3. Visit gm.com and gm.ca 4. Close browser 5. Verify that the count attributes of the two new sites are identical (1) 6. Open browser to a new tab 7. Enter ‘gm’ into the url bar 8. Verify that the most recently visited of the two gm sites is the first entry in the history auto-suggest list
…ount * Re-order results to show history items before bookmark items * Record number of times site is visited * Re-order history items based on number of times visited and last access timestamp * Update and create tests Fixes: #3049 Auditors: @bbondy Test plan: A new attribute, count, is added to history items in the sites section of save-session-1. This attribute records the number of times a site has been accessed. The test plan is broken in two components, one to verify the count attribute is incremented on access, the second to verify that the count and last access time are used when sorting history suggestions. Scenario 1 Part A 1. Clear save-session-1 2. Access a site 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has a value of 1 Part B 1. Open browser 2. Navigate to site from Part A 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has an incremented value Scenario 2 1. Clear save-session-1 2. Open browser 3. Visit gm.com and gm.ca 4. Close browser 5. Verify that the count attributes of the two new sites are identical (1) 6. Open browser to a new tab 7. Enter ‘gm’ into the url bar 8. Verify that the most recently visited of the two gm sites is the first entry in the history auto-suggest list
…ount * Re-order results to show history items before bookmark items * Record number of times site is visited * Re-order history items based on number of times visited and last access timestamp * Update and create tests Fixes: #3049 Auditors: @bbondy Test plan: A new attribute, count, is added to history items in the sites section of save-session-1. This attribute records the number of times a site has been accessed. The test plan is broken in two components, one to verify the count attribute is incremented on access, the second to verify that the count and last access time are used when sorting history suggestions. Scenario 1 Part A 1. Clear save-session-1 2. Access a site 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has a value of 1 Part B 1. Open browser 2. Navigate to site from Part A 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has an incremented value Scenario 2 1. Clear save-session-1 2. Open browser 3. Visit gm.com and gm.ca 4. Close browser 5. Verify that the count attributes of the two new sites are identical (1) 6. Open browser to a new tab 7. Enter ‘gm’ into the url bar 8. Verify that the most recently visited of the two gm sites is the first entry in the history auto-suggest list
…ount * Re-order results to show history items before bookmark items * Record number of times site is visited * Re-order history items based on number of times visited and last access timestamp * Update and create tests Fixes: #3049 Auditors: @bbondy Test plan: A new attribute, count, is added to history items in the sites section of save-session-1. This attribute records the number of times a site has been accessed. The test plan is broken in two components, one to verify the count attribute is incremented on access, the second to verify that the count and last access time are used when sorting history suggestions. Scenario 1 Part A 1. Clear save-session-1 2. Access a site 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has a value of 1 Part B 1. Open browser 2. Navigate to site from Part A 3. Close browser 4. Verify that the count attribute for the saved site in save-session-1 has an incremented value Scenario 2 1. Clear save-session-1 2. Open browser 3. Visit gm.com and gm.ca 4. Close browser 5. Verify that the count attributes of the two new sites are identical (1) 6. Open browser to a new tab 7. Enter ‘gm’ into the url bar 8. Verify that the most recently visited of the two gm sites is the first entry in the history auto-suggest list
This does not seem to work for me. I've built it from master 497ecf8 and installed it on my system. I've did the following:
Should 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 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 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 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 |
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:
The text was updated successfully, but these errors were encountered: