Comment 10 for bug 734581

This isn't that useful if we have a completion feature for previous viewed websites. For example, if "http://www.cats.com" , then press the completion key, if there are "http://www.cats.com" and "http://www.cats.net" in your history it should show a drop-down menu like it does for boomarked URLs. If there are no matches, it already shows a "Search with ..." link, which is useful IMO.

If the user is browsing undiscovered websites, then perhaps this feature should see which domains exist, and generate the ambiguity drop-down list based on that, in which case it should be an extension instead.

A different key combination for each generic top-level domain is a bad idea because it is not extendable (are we going to have different key bindings for each gTLD and protocol? i don't think so).

Can we agree that if a feature is adopted, but no key combination is decided, that it can be adopted without a default key combination (the user chooses his own from available keys in their own setup)?