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.

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

How to completely disable heuristic item in unified autocomplete?

  • 4 fhreagra
  • 1 leis an bhfadhb seo
  • 2 views
  • Freagra is déanaí ó wareya

more options

The latest developer builds of Firefox have removed the ability to disable unified autocomplete. I used to disable unified autocomplete in order to get rid of the top element ("search on google", etc), but this is no longer possible.

The styling workaround in https://support.mozilla.org/en-US/questions/1100367 is not appropriate, because using the arrow keys to navigate down the URL bar still selects the heuristic result. I need to *completely* disable the heuristic result, so that it is 100% completely inaccessible.

None of the about:config flags under browser.urlbar in 49.0a2 (2016-06-18) are capable of disabling the heuristic result without entirely disabling autocomplete/suggestions, which is not the desired behavior. I need a functioning autocomplete dropdown that contains no heuristic result, neither visually nor in keyboard navigation.

The latest developer builds of Firefox have removed the ability to disable unified autocomplete. I used to disable unified autocomplete in order to get rid of the top element ("search on google", etc), but this is no longer possible. The styling workaround in https://support.mozilla.org/en-US/questions/1100367 is not appropriate, because using the arrow keys to navigate down the URL bar still selects the heuristic result. I need to *completely* disable the heuristic result, so that it is 100% completely inaccessible. None of the about:config flags under browser.urlbar in 49.0a2 (2016-06-18) are capable of disabling the heuristic result without entirely disabling autocomplete/suggestions, which is not the desired behavior. I need a functioning autocomplete dropdown that contains no heuristic result, neither visually nor in keyboard navigation.

Réiteach roghnaithe

There was a funky three-way conflict between the specific version of aurora I was running, an addon I use, and the custom CSS. Updating aurora again fixed the problem.

Read this answer in context 👍 0

All Replies (4)

more options

See:

more options

The chosen solution in that question does not prevent the entry from being selected with the keyboard. If I type in part of a URL I have to press down twice in order to reach the first actual result.

I need to completely disable the heuristic item, not just hide it.

more options

Hmm, display:none works for me in Portable Developer Edition 49.0a2. When I press the down arrow from the URL bar, Firefox selects the first visible item, but I only tested with a couple of strings. I used this in Stylish:

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul); /* Firefox 49 "Visit..." or "Search..." bar in the drop-down */ #PopupAutoCompleteRichResult richlistitem[actiontype="searchengine"], #PopupAutoCompleteRichResult richlistitem[actiontype="visiturl"] { display:none !important; } /* Increase height to avoid scroll bar - Firefox 49 inline URL style */ #PopupAutoCompleteRichResult .autocomplete-richlistbox { height: auto !important; max-height: calc(30px * (12 - 1)) !important; }

Note: This also hides search suggestions if they are turned on.

Note: I suggest launching a new window to test style rule mods for the URL bar and Search bar because some of them seem not to have any effect in existing windows.

Edit: Corrected an error with the wiki markup in the @namespace line.

Athraithe ag jscher2000 - Support Volunteer ar

more options

Réiteach Roghnaithe

There was a funky three-way conflict between the specific version of aurora I was running, an addon I use, and the custom CSS. Updating aurora again fixed the problem.