We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox no longer respects browser.fixup.alternate.enabled

  • 7 个回答
  • 1 人有此问题
  • 6 次查看
  • 最后回复者为 randomanon

more options

After updating to Firefox 59.0.2 from Firefox 57.0, the browser now ignores browser.fixup.alternate.enabled. A similar issue seems to be happening in other versions of Firefox, according to previous questions.

After updating to Firefox 59.0.2 from Firefox 57.0, the browser now ignores browser.fixup.alternate.enabled. A similar issue seems to be happening in other versions of Firefox, according to previous questions.

被采纳的解决方案

jscher2000 said

The top line of the autocomplete drop-down should indicate what will happen if you press Enter or click the Go button with the current contents of the address bar. If Firefox starts showing a previously visited address as soon as you start typing, before you type a period, that's usually due to autofill which suggests top level site addresses in the address bar. There's a setting to disable that. If the problem occurs with text that contains a period and no spaces (like window.open), Firefox will always check whether they are domain names before searching. A workaround is to type an apostrophe at the beginning so Firefox knows it is not a valid URL. This screenshot illustrates what I'm getting at:

Thanks for the suggestion, the use of an apostrophe to make Firefox recognize something is not a url should help.

Some other notes, should the problem happen in the future: No suggestions appeared in the url bar, and Firefox was automatically adding .com or .net to whatever was typed, despite no periods being entered.

The following about:config preferences were disabled:

  1. browser.fixup.alternate.enabled
  2. browser.urlbar.suggest.bookmark
  3. browser.urlbar.suggest.history
  4. browser.urlbar.suggest.openpage
  5. browser.urlbar.suggest.searches
  6. browser.urlbar.autoFill
  7. browser.urlbar.autocomplete.enabled
定位到答案原位置 👍 0

所有回复 (7)

more options

randomanon said

After updating to Firefox 59.0.2 from Firefox 57.0, the browser now ignores browser.fixup.alternate.enabled. A similar issue seems to be happening in other versions of Firefox, according to previous questions.

Hi,

Could you be a bit more specific, please  ?

In what way does Firefox ignore that preference  ?

more options

The fixup only works for http and not for other protocols including https.

more options

Enigma said

randomanon said
After updating to Firefox 59.0.2 from Firefox 57.0, the browser now ignores browser.fixup.alternate.enabled. A similar issue seems to be happening in other versions of Firefox, according to previous questions.

Hi,

Could you be a bit more specific, please  ?

In what way does Firefox ignore that preference  ?

Although browser.fixup.alternate.enabled was set to false, Firefox was still predicting URLs by adding www. and .com/.net at random to keywords typed in the address bar after pressing enter.

由randomanon于修改

more options

randomanon said

Although browser.fixup.alternate.enabled was set to false, Firefox was still predicting URLs by adding www. and .com/.net at random to keywords typed in the address bar after pressing enter.

Thank you for clarifying that  !

Now that you've read cor-el's post, you know why, right  ?

more options

When they say the fixup only works for http and not https, does it mean the browser will continue predicting for https urls, regardless of settings, or does it mean the browser only autocorrects to http urls?

If what they said meant the former, what would be a solution that prevents url prediction for all protocols?

more options

The top line of the autocomplete drop-down should indicate what will happen if you press Enter or click the Go button with the current contents of the address bar. If Firefox starts showing a previously visited address as soon as you start typing, before you type a period, that's usually due to autofill which suggests top level site addresses in the address bar. There's a setting to disable that.

If the problem occurs with text that contains a period and no spaces (like window.open), Firefox will always check whether they are domain names before searching. A workaround is to type an apostrophe at the beginning so Firefox knows it is not a valid URL.

This screenshot illustrates what I'm getting at:

more options

选择的解决方案

jscher2000 said

The top line of the autocomplete drop-down should indicate what will happen if you press Enter or click the Go button with the current contents of the address bar. If Firefox starts showing a previously visited address as soon as you start typing, before you type a period, that's usually due to autofill which suggests top level site addresses in the address bar. There's a setting to disable that. If the problem occurs with text that contains a period and no spaces (like window.open), Firefox will always check whether they are domain names before searching. A workaround is to type an apostrophe at the beginning so Firefox knows it is not a valid URL. This screenshot illustrates what I'm getting at:

Thanks for the suggestion, the use of an apostrophe to make Firefox recognize something is not a url should help.

Some other notes, should the problem happen in the future: No suggestions appeared in the url bar, and Firefox was automatically adding .com or .net to whatever was typed, despite no periods being entered.

The following about:config preferences were disabled:

  1. browser.fixup.alternate.enabled
  2. browser.urlbar.suggest.bookmark
  3. browser.urlbar.suggest.history
  4. browser.urlbar.suggest.openpage
  5. browser.urlbar.suggest.searches
  6. browser.urlbar.autoFill
  7. browser.urlbar.autocomplete.enabled