(In reply to Filip Š from comment #87) > Would it be possible to have something like this (additional pref), but only > for searches that contain (at least one) dot? This would be useful because > most commonly, searches without dots are not used as domains (except > `localhost` which is handled separately), while searches containing dots > could be commonly used as domains.
I don't see why, searches without dots are also used a lot in enterprise. I gave you two solutions that cover your use case pretty well depending on the needs, there are also ways to always force a visit (type the protocol) or always force a search (prepend ?). I don't think we should make the code even more complex for every edge case. > Also, I don't know if it's just for me, but Firefox takes longer to "resolve" (try resolving but then fail and search instead) domains without dots (`for example `test`, which takes few seconds before redirecting to search) that domains with dots (for example `test.aaaaa`, which is redirected to search almost immediately). I'm still working on bug 1398567 that may help there. > What about whitelisting whole TLDs/suffixes? And along with this, API that allows extensions to modify the list of whitelisted TLDs would be quite useful, for example for extensions that provide support for domains like `.eth` or `.bit`. I don't think extensions should be necessary, you can file an enhancement bug for whitelisting suffixes and we can eval that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263505 Title: Wishlist: add "use input as a search term" to "address not found" page To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
