This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Typing text into the address field triggers a search, even when the separate search field is enabled and the "address field search" is disabled in preferences

  • 2 antwoorde
  • 1 het hierdie probleem
  • 2 views
  • Laaste antwoord deur denzl

denzl
denzl
more options

Since one of the last updates (currently using 78.0.2esr on mac), the address field doesn't behave as expected and not as it did before: For example, when I type "wiki.dtpd.loc" into the address field, Firefox should open this (local) Webpage. Instead, it triggers a Google search for the term "wiki.dtpd.loc". My Firefox is configured to show separate address and search fields, and NOT to use the address field for search suggestions, so this shouldn't happen.

It is annyoing, 'cause I can't access my local pages without alway prefixing them with http:// or https://

Is there a solution? Is it a bug?

Thanks ;-)

Since one of the last updates (currently using 78.0.2esr on mac), the address field doesn't behave as expected and not as it did before: For example, when I type "wiki.dtpd.loc" into the address field, Firefox should open this (local) Webpage. Instead, it triggers a Google search for the term "wiki.dtpd.loc". My Firefox is configured to show separate address and search fields, and NOT to use the address field for search suggestions, so this shouldn't happen. It is annyoing, 'cause I can't access my local pages without alway prefixing them with http:// or https:// Is there a solution? Is it a bug? Thanks ;-)

Gekose oplossing

Try to set keyword.enabled = false on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

Lees dié antwoord in konteks 👍 1

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Gekose oplossing

Try to set keyword.enabled = false on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

denzl
denzl Vraag-eienaar
more options

Perfect, thanks co-rel ;-)