Bugzilla

ideally when it happens the user has recently typed the same string and picked exactly that url from the list.

There are a few options we could evaluate to address the problem:
 * always add the bare domain result at a tab distance, so we provide an escape and a way to train the system. Though this means wasting a potential result.
 * allow to dismiss a suggestion as not good. Though this requires a discoverable button/menu we don't have yet, it's planned for the future.
 * Check if the url has a frecency over a certain threshold, the user may not be likely to want to visit a site that was visited rarely or just once... the problem is defining such threshold. Plus it's not given that a url is good for autofill regardless of how many times it was visited (indeed it would be nice to have a blocklist of domains that should not autofill urls).

ideally when it happens the user has recently typed the same string and picked exactly that url from the list.

There are a few options we could evaluate to address the problem:
 * always add the bare domain result at a tab distance, so we provide an escape and a way to train the system. This means wasting a potential result but it could be a valid short term solution. Of course it should happen if we'd have autofilled the bare domain.
 * allow to dismiss a suggestion as not good. Though this requires a discoverable button/menu we don't have yet, it's planned for the future.
 * Check if the url has a frecency over a certain threshold, the user may not be likely to want to visit a site that was visited rarely or just once... the problem is defining such threshold. Plus it's not given that a url is good for autofill regardless of how many times it was visited (indeed it would be nice to have a blocklist of domains that should not autofill urls).

ideally when it happens the user has recently typed the same string and picked exactly that url from the list.

There are a few options we could evaluate to address the problem:
 * always add the bare domain result at a tab distance, so we provide an escape and a way to train the system. This means wasting a potential result but it could be a valid short term solution. Of course it should happen if we'd have autofilled the bare domain.
 * allow to dismiss a suggestion as not good. Best long term though this requires a discoverable button/menu we don't have yet, it's planned for the future.
 * Check if the url has a frecency over a certain threshold, the user may not be likely to want to visit a site that was visited rarely or just once... the problem is defining such threshold. Plus it's not given that a url is good for autofill regardless of how many times it was visited (indeed it would be nice to have a blocklist of domains that should not autofill urls).