Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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 ответа
  • 1 имеет эту проблему
  • 2 просмотра
  • Последний ответ от 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 ;-)

Выбранное решение

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.

Прочитайте этот ответ в контексте 👍 1

Все ответы (2)

more options

Выбранное решение

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 ;-)