The current scope is to provide an experience identical to the old bar, to 
limit the confusion for users and QA, but it could surely be one of the things 
we want to do sooner than later.
Should we use it through nsIEffectiveTLDService? I just tried to use 
getPublicSuffixFromHost, but it doesn't seem to do any kind of verification, it 
doesn't seem to have a strict option, so I assume we'd have to add a new method 
to check a given host.

-- 
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:
  Confirmed
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