browser.urlbar.update1 no longer works
Categories
(Firefox :: Address Bar, defect)
Tracking
()
People
(Reporter: admin, Unassigned)
Details
I can't get the new url bar to disable anymore via this about:config. In the mean time is there a work around? Any changes I can make to the build scripts to compile firefox without the megabar?
|
||
Comment 1•5 years ago
|
||
I need the old-style address bar too. The history drop-down for the new one is far too narrow for me -- I use the history a lot in order to navigate through recent URLs. I need to be able to see as much of the URL as possible. The older history drop-down uses the full window width, but the new address bar in Firefox 75 / 77 constrains the drop-down to the width of the URL bar itself.
This is a major UX flaw for me, and makes the browser much more frustrating to use.
|
||
Comment 2•5 years ago
|
||
I'm afraid that option was removed in bug 1627969.
If are you looking for a pref to avoid opening the Top Sites on click, we have bug 1627858
|
||
Comment 3•5 years ago
|
||
If you have issues with UI movements, you can evaluate the prefers-reduced-motion option that, from Firefox 78, on will remove the input field expansion effect. See https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion
There's no plan to change the results panel width at this time.
|
|
||
Comment 4•5 years ago
|
||
Just as a side note, check your toolbar customization. For example if you have the spacers around the urlbar, you can easily remove them by right clicking and removing from the toolbar. You can also execute most of the search operations in the urlbar itself, so if you still have the separate search bar and don't use it often, you may evaluate removing it.
Like I have always set keyword.enabled to false. I don't want a typo in a URL to leak to a search engine. So I certainly would not remove the separate search bar.
|
|
||
Comment 6•5 years ago
|
||
We have some plans to reduce the risk of accidentally hitting one-off buttons and send things to the search engine, that will pretty much allow to opt-in into a search-only mode from an url-only mode, so potentially in the future that "search leak" problem won't exist.
Description
•