Why'd the settings stop working for search to stay in search?
I set the about:config settings when I got the new computer early last year. It's been working fine. Suddenly, searches are popping up again to the urlbar.
browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar is still set to false. Keyword.enabled is still set to false.
I see a couple of site references to browser.fixup.alternate.enabled, but it doesn't exist.
How do I get FF back to proper search in the search bar?
Réiteach roghnaithe
Hi,
Sorry for the inconvenience. The team is working on implementing a modern embedded search UI for the New Tab. As TyDraniu said, unfortunately, you won't be able to change that behavior for now. The old code has been removed to clean up space for the new one.
Read this answer in context 👍 0All Replies (8)
Hello
For illustration, browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar. https://connect.mozilla.org/t5/discussions/address-bar-updates-now-live-in-firefox-nightly/m-p/97642/highlight/true#M38055
Under Firefox 147. browser.fixup.alternate.enabled, the preference is not available in about:config. browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar, the preference is available in about:config and works.
A subject. https://support.mozilla.org/en-US/questions/1560246
Mozilla needs to change that page, then.
I must have found the handoff parameter before, because it's set to false. The handoff is still happening. That's a problem.
We don't use that pref anymore. Right now that search component is under heavy development, devs removed that pref to make it easier.
Terrible UX. They're supposed to make things easier for us, not for them.
Réiteach Roghnaithe
Hi,
Sorry for the inconvenience. The team is working on implementing a modern embedded search UI for the New Tab. As TyDraniu said, unfortunately, you won't be able to change that behavior for now. The old code has been removed to clean up space for the new one.
Yet it still works on my slightly older laptop, also with W11. Only the desktop has changed functionality.
Also, competent coding waits until the new code is ready before killing something that works.
Also, competent coding waits until the new code is ready before killing something that works.
You are absolutely right. Unfortunately, in this case, it was too complex to maintain both versions at the same time. Sorry once again.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.