2

I set Firefox to install updates automatically and installed one recently. This new version no longer uses the address bar for search, i.e. if I type "some random search", it is trimmed to "some" and redirected to "www.some.com", which is the navigation behavior and not the search behavior.

The keyword searches still work, i.e. "d some random search" where "d" is the keyword for DuckDuckGo web search. Without a search keyword, I expect Firefox to use the default search engine and instead I have the behaviour above.

I checked the settings and Search bar is at "Use the address bar for search and navigation":

Firefox search bar behavior

If I change it "Add search in toolbar", the behavior of the address bar is the same but the search bar doesn't work either.

My system is macOS 10.14.5; the Firefox version history shows:

Firefox 68.0 (20190705220548)
Details
Installed on: 12 July 2019, 11:03:07
Status: The Update was successfully installed

I have no add-ons or extensions installed. I believe this is a bug and should affect many people. Has anyone found a fix?

Improve this question
5
  • 1
    Verify that the problem isn't an extension. Restart Firefox in safe mode (you can do that from about:profiles, there's a button for "Restart with add-ons disabled").
    – fixer1234
    Commented Jul 13, 2019 at 19:28
  • Restarting in Safe Mode has none of these problems, and seems to have fixed the problem, as now when I restart normally again the problems are gone.
    – emonigma
    Commented Jul 14, 2019 at 9:07
  • @fixer1234 I have no add-ons or extensions installed, by the way.
    – emonigma
    Commented Jul 15, 2019 at 14:42
  • All solved, I presume? :)
    – BoffinBrain
    Commented Oct 23, 2019 at 21:06
  • @BoffinBrain Yes, and I added an answer.
    – emonigma
    Commented Nov 1, 2019 at 15:38

1 Answer 1

Reset to default
0

I reported a bug at BugZilla. I had the problem with versions 68.0 and 69.0, but the bug seemed solved by restarting Firefox, so I was not able to get the details requested from the bug report and the bug report was closed.

I tested again last week when Firefox auto-updated to 70.0.1 and I did not have this behavior, so the problem seems gone for good.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .