Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

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 Antworten
  • 1 hat dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von 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 ;-)

Ausgewählte Lösung

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.

Diese Antwort im Kontext lesen 👍 1

Alle Antworten (2)

more options

Ausgewählte Lösung

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.

more options

Perfect, thanks co-rel ;-)