I want to provide some feedback about this change and see if this can be
fixed:

For general usage, this change is good and better than redirecting users
to unexisting websites when they want to search.

However, there are some TLDs that aren't present in the Public Suffix
List, which means that users who want to visit such domains will instead
be redirected to search. Example of such domains are local/reserved TLDs
(like `.local` or `.test`) which are commonly used for local
development/testing, as well as non-IANA-managed TLDs, like OpenNIC
(`.oss,` `.libre`...) and others, mostly by some decentralized projects
(`.eth`, `.bit`...).

All of them now just trigger a search. To access them, you now need to
manually type `http://` or `https://` before the domain. Are there any
other better solutions? Could Firefox try to resolve such domains to see
if they contain existing website (for local/reserved TLDs and OpenNIC
which are commonly resolved with custom `/etc/hosts` file or custom DNS
server) and provide some API to extensions so that extensions will be
able to tell it that TLDs are valid (for `.eth`, `.bit`... which are
commonly resolved through extensions).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/263505

Title:
  Wishlist: add "use input as a search term" to "address not found" page

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  Altogether too often when I get the "Address Not Found" page, it is
  because I expected too much from the Wonderful Bar or whatever it's
  called.  It would be a useful addition if the "Address Not Found" page
  could offer the option to use the stuff you typed into the location
  bar as input for your designated search engine, and/or perform history
  search on those terms.  (For me, the former is the more useful, but I
  expect both would be handy, and the effort to offer both is probably
  marginal if you decide to do one or the other.)

  All to often, what you typed in is no longer visible in the location
  bar, because http:// gets prepended and sometimes a .com appended to
  what is displayed in the location bar at the point you get the
  "Address Not Found" error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/263505/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to