User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20160814004012 Steps to reproduce: Type a few letters in the url bar. Actual results: At the top of the list of suggestions, an option "Visit [auto-completed domain in urlbar]" appears. Expected results: I had set browser.urlbar.unifiedcomplete to false in about:config precisely to disable this feature. Apparently since a recent version (48?), this no longer works. It goes against the workflow of lots of people, so there should be a way to turn it off. For us, it seems like just clutter, because the action is already available by simply pressing "return". Also see Bug 1224801, Bug 1072351, and the following support questions: https://support.mozilla.org/en-US/questions/1115273 https://support.mozilla.org/en-US/questions/1099228

This is working as designed. browser.urlbar.unifiedcomplete was never meant to be a user pref, it was just a kill switch to disable the feature in case any issues were discovered too late in the release cycle. Now that the feature is working as expected, there is no more a use for the kill switch.

I understand, but then the solution is not to bring back that old config value, but to create another way to disable that top "Visit [...]" option. It's not that we don't want the new mixed suggestion results, it's just that we don't want that top option.

If the issue you have with that line is the vertical space it takes, we have bug 1235397 to merge it in the URL bar, but it is hard. As far as behavior goes, there has been no change when the "Visit" line was introduced, it serves as a hint as to what happens if you hit the Enter key.

I see, thank you for the information, that is indeed the issue most of us are having. Perhaps it would be nice if someone created a temporary solution using a userChrome.css file or something, that simply hides that line. I'm not sure how to target that line myself with a css rule ...

(In reply to Joris Debonnet from comment #4) > I see, thank you for the information, that is indeed the issue most of us > are having. Perhaps it would be nice if someone created a temporary solution > using a userChrome.css I'm sure someone did that on the Firefox Reddit.

Indeed; actually I found a solution here: https://support.mozilla.org/en-US/questions/1125487 Just in case someone else ends up here looking for one...