Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Autocomplete is not very accurate and yields wrong results #4979

Closed
Sh1d0w opened this issue Oct 20, 2016 · 3 comments
Closed

Autocomplete is not very accurate and yields wrong results #4979

Sh1d0w opened this issue Oct 20, 2016 · 3 comments
Assignees
Labels

Comments

@Sh1d0w
Copy link

Sh1d0w commented Oct 20, 2016

Did you search for similar issues before submitting this one?

No.

Describe the issue you encountered:

When I type in the Url bar I don't get the most relevant results that I should get.

I demonstrate this in the following video: http://webm.land/media/n5dh.webm

  1. I started to type ve . The one and only website that I have visited and starts with ve is vesti.bg . But as you can see I get irellevant results from developer.chrome .... because it contains ve but it is in the middle of the word and I have visited it recently than vesti.bg.

The correct result appears if I continue to type and there are no other matches in the history, e.g. if I type ves.

This is probably related to #4955 , but I think it has to be fixed in this milestone, because the wrong behaviour is also intorduced in this milestone. If you think this is duplicate report of #4955 please close the issue.

Expected behavior:

I should get accurate results. The check for a matching and order the results by exact domain name match, rather than random occurences in the domain name.

@wmeyer48
Copy link

I have noticed a great deal of difficulty manually typing the URL in the latest update (0.12.5). Turning off the history match eliminates the difficulty, so I would have to guess you need to do some serious optimization in that area. The observed behavior is dropped keystrokes, so youtube might become yotue. Not pleasant.

@Sh1d0w
Copy link
Author

Sh1d0w commented Oct 20, 2016

@wmeyer48 The problem with the disappearing characters is reported and fixed in v.0.12.6 (#4731). Just wait a little bit more to be released :)

@aekeus
Copy link
Member

aekeus commented Oct 20, 2016

I think this is duplicate, so closing. Please re-open if the next preview release has the same issue.

@aekeus aekeus closed this as completed Oct 20, 2016
@luixxiul luixxiul added the duplicate Issue has already been reported label Oct 21, 2016
@luixxiul luixxiul removed this from the 0.12.6dev milestone Oct 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants