Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Awesome Bar: auto-complete suggestion does not remember port number from URL

  • 2 àwọn èsì
  • 6 ní àwọn ìṣòro yìí
  • 4 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ noregistrationplease

noregistrationplease
noregistrationplease
more options

I visit URLs with non-standard ports all the time such as http://localhost:8080.

When I start typing "localhost" into the address bar, the Awesome Bar suggests only "http://localhost" - i.e. WITHOUT the port 8080 - instead of suggesting the full URL including the port.

I never visit "localhost" without port 8080 so that entry should not even be in my history at all.

The Awesome Bar should always remember port numbers when making suggestions.

I visit URLs with non-standard ports all the time such as http://localhost:8080. When I start typing "localhost" into the address bar, the Awesome Bar suggests only "http://localhost" - i.e. WITHOUT the port 8080 - instead of suggesting the full URL including the port. I never visit "localhost" without port 8080 so that entry should not even be in my history at all. The Awesome Bar should always remember port numbers when making suggestions.

All Replies (2)

philipp
philipp
  • Moderator
more options

hello, as a workaround you could try to bookmark those addresses & see if they will be included in the auto-complete suggestions this way.

noregistrationplease
noregistrationplease Ìbéèrè olóhun
more options

Unfortunately that doesn't work. Even with the URL bookmarked, typing "local" to begin the autocomplete still results in the URL being auto-completed without a port number.

Typing the name of the bookmark itself results in no auto-complete at all, meaning you still have to press the down arrow before hitting "return" to get to the correct URL. So you're back at square one.

I filed a bug here: https://bugzilla.mozilla.org/show_bug.cgi?id=853898

Which turned out to be a duplicate of: https://bugzilla.mozilla.org/show_bug.cgi?id=764062