I mean, at least they're trying, I guess. Still seems to me like lipstick on a pig.
I'm still trying to figure out what UX problem the expanding bar was intended to address.
I mean, at least they're trying, I guess. Still seems to me like lipstick on a pig.
I'm still trying to figure out what UX problem the expanding bar was intended to address.
I'm using up-to-date Firefox, but I toggled the about:config flag to get the old address bar, figuring I may as well use it while I can. Here is what the address bar looks like for me:
Focused: https://i.ibb.co/TWDw9WL/Screen-Shot-2020-05-05-at-5-30-57-P...
Unfocused: https://i.ibb.co/QHd0SBm/Screen-Shot-2020-05-05-at-5-31-01-P...
Do you not see the blue focus outline? It's pretty thick!
edit: just remembered because it happened again. I'm not sure if it's related but I often find now that when I type "n" the bar doesn't autocomplete "ews.ycombinator.com" with the rest of the text highlighted anymore. It still goes there if I hit enter, though.
I'm just so perplexed by the whole thing.
I have a browser profile that is used almost exclusively for amazon content as well. The most visited links in that profile are amazon.co.uk and prime video but the only "most frequent" links it would show were on twitch and the occasional youtube page I visited to find trailers for amazon hosted videos.
When I went to about:config and toggled the four "update1" bools to false, amazon came back in my "most frequent" links.
Pretty strange, eh?
Edit: so I just installed 76, and switched the four "browser.urlbar.update1" bools that enable this back to "true", and again, any amazon.co.uk links are removed from the list I get when clicking on the empty urlbar.
I don't really care about the ugly styling, but since this is a navigation feature I use extensively, I'm turning the whole thing off again. Hope they fix (or document) this before the choice disappears!
Normally (in my setup) it shows a list of "most visited" urls.
The new behaviour is to still show this list but omit any amazon.co.uk (and maybe other, I have no idea) urls.
Completion works as expected as far as I know.
My "new tab page" is always set to just blank page and has been for years. I dislike all the fancy new page stuff and just set it to blank page on initial install.
The sites that show up in the urlbar dropdown are frequently visited ones, same as the ones that show up when I turn the "update1" stuff off, or the ones prior to ff 75, just not sites containing amazon.co.uk.
So while I don't doubt your information, it doesn't make sense to me as an explanation. Maybe not having any sites in a new tab page is some kind of corner case that exposes a bug. It's weird that amazon is specifically affected though!
My GF hates it because it partially obscures the bookmarks toolbar on any new tab. So her everyday usage is impacted where she opens firefox and clicks a bookmark. She hated it so much she looked through reddit threads and modified her about:config to make it go away, which is really saying something.
I just hope they don't remove the disable recipe.
(about:config browser.urlbar.update1 -> false)
I guess I'll head back to SeaMonkey now. The UI hasn't changed in a decade but at least the UI hasn't changed in a decade.
Yes.
Edit: Actually, nothing works on Dev Edition anymore. No matter what I toggle, the stupid location bar expands when you click on it.
> Firefox simply wanted it to be more obvious that the address bar is in focus the moment you open a new tab.
Is that it? Because I'm still trying to figure this out! I'm just really surprised that this was a problem for a substantial number of users—the address bar already had a very prominent focus state with its thick blue outline.
I'd even argue that indifference should be the goal when making design changes; make subtle changes over time instead of the complete overhauls that are common today.
If everyone is indifferent, why did you change anything?
Also, people quickly get used to suboptimal UI and all kinds of UI bugs. Fixing those bugs improves the experience for new users while acclimatized users will be indifferent or even hostile to the change. It's a classic dilemma for long-lived products.
Either I never noticed or that very prominent focus state was invisible in the theme I installed. So yes, it was definitely one of the most regular issues I had with Firefox and now it's fixed. Not in the most elegant way but it works for me.
Indifference among people already using Firefox is a good outcome if it is viewed favorably by people new to Firefox, which is who I would guess these kinds of changes are aimed at.
Let me know if I've got the issue wrong.
And who knows, maybe Mozilla is right—but I wonder if they've actually done large-scale feedback gathering. This isn't the sort of thing you can suss out just from looking at analytics.
Some have Bing as their homepage, if you've ever done IT training you might know the next line. They do it differently, they type "Google", click a link to go to Google, then type "BBC" (say), and click on the link for "bbc.co.uk". It's insane.
But the problem with the current about:config flag is it's actually changing the entire code pathway, and is going to be removed in a couple months!
[0] https://www.ghacks.net/2020/04/08/how-to-restore-the-old-fir...
For me, the bigger address bar is just as bad as an advertisement: it's trying to steal my attention, except in this case no one else is benefiting from doing so.
If they remove the option, I hope someone smarter than me can come-up with an add-on to fix it.
Furthermore, Firefox extensions don't have the capability to mess with the address bar.
Awful. As soon as it can't be turned off, that's the moment I'll finally stop using the browser.
It breaks absolutely "normal" expectations of a GUI.
https://windows-cdn.softpedia.com/screenshots/miranda-im_12....
The picture you posted is a positive example. An example on how to customize the software you use.
Possibly the same as removing navigation arrows from the context menu if text is selected, i.e. to annoy long time Firefox users like me?
Certain features should be compile time options, default off and then we could make a UX-designer edition with all the crazy stuff just line we have developer edition.
Then I and everyone else could continue you use the old ux that actually worked very well ;-)