Live data from Hacker News

Firefox 76

mozilla.org

71–80 of 274 posts

Re: Firefox 76

#71

Earlier quoted context omitted.

Seconded. I prefer it to the old design. But we seem to be the minority.

It's just the HN effect; complain about the most minute details. Firefox simply wanted it to be more obvious that the address bar is in focus the moment you open a new tab.

Reddit was pretty annoyed too. I actually did a little real-life poll (I admittedly might care about minute details too much!), and everyone was either indifferent or negative. Indifference was more common, but, is that really a good outcome?

> 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.

Re: Firefox 76

#72

> The shadow around the address bar field is reduced in width when a new tab is opened; 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.

They should just put a toggle for it under the Customization page. I think that would be the simplest way to placate peope that dislike it. (Yes I know you can about:config to fix it, but a toggle makes more sense.)

Re: Firefox 76

#73

Earlier quoted context omitted.

Ironically though, I wonder if not using Firefox much is the cause of that annoyance. In other words, Firefox usually waits for an opportune time to update, but if it's been closed for a long time, it likely decides that it's too out of date, and updating asap is critical for security. I'll reiterate my recommendation for ESR, it's Firefox but for people who want less frequent updates. :)

Firefox ESR updates on the same frequency as the mainline release, they're just more limited in scope (i.e. mostly just security & stability fixes).

They should be smaller downloads that install more quickly though, shouldn't they?

I'm not on Firefox ESR, but switching to Windows LTSC made Windows updates a lot less painful and less noticeable, even though technically the frequency is the same.

Re: Firefox 76

#74

> The shadow around the address bar field is reduced in width when a new tab is opened; 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.

They should just put a toggle for it under the Customization page. I think that would be the simplest way to placate peope that dislike it. (Yes I know you can about:config to fix it, but a toggle makes more sense.)

As much as I think the change is stupid for everyone, I'd be placated well enough with just an about:config toggle.

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!

Re: Firefox 76

#75

> The shadow around the address bar field is reduced in width when a new tab is opened; 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.

They should just put a toggle for it under the Customization page. I think that would be the simplest way to placate peope that dislike it. (Yes I know you can about:config to fix it, but a toggle makes more sense.)

What do you change in about:config to change it? It's been driving me crazy since they implemented it.

Re: Firefox 76

#76

i just want to say, Firefox is seriously fast now, while Chrome continues to get slower [1]. my 10M datapoint uPlot benchmark runs in half the time, for both pure js (fake data gen) and canvas workloads (chart rendering). check out the console in [2]. however, i'm still waiting for the performance assessment in devtools to improve so i can get an easy summary as i can in Chrome. also, better default form input stylin…

> also, better default form input styling would be nice. it's so...Windows 98....but i'm on Windows 10. :\

Google and Microsoft seem to agree with you, but I totally don't get it!

If the website doesn't specify a style, my browser should fall back to a design that matches my OS, not whatever the browser developer thought was pretty!

And if Windows is coming back and telling the browser to use Windows 98 styled buttons, Microsoft should fix Windows!

Re: Firefox 76

#77
post #55

Earlier quoted context omitted.

I don't use Firefox often because of the constant updating that prevents me from using it right away. Chrome and Brave don't seem to do that, at least not in the same obvious way that Firefox does.

Ironically though, I wonder if not using Firefox much is the cause of that annoyance. In other words, Firefox usually waits for an opportune time to update, but if it's been closed for a long time, it likely decides that it's too out of date, and updating asap is critical for security. I'll reiterate my recommendation for ESR, it's Firefox but for people who want less frequent updates. :)

[deleted]

Re: Firefox 76

#78

Earlier quoted context omitted.

They should just put a toggle for it under the Customization page. I think that would be the simplest way to placate peope that dislike it. (Yes I know you can about:config to fix it, but a toggle makes more sense.)

What do you change in about:config to change it? It's been driving me crazy since they implemented it.

[deleted]

Re: Firefox 76

#79

i just want to say, Firefox is seriously fast now, while Chrome continues to get slower [1]. my 10M datapoint uPlot benchmark runs in half the time, for both pure js (fake data gen) and canvas workloads (chart rendering). check out the console in [2]. however, i'm still waiting for the performance assessment in devtools to improve so i can get an easy summary as i can in Chrome. also, better default form input stylin…

> also, better default form input styling would be nice. it's so...Windows 98....but i'm on Windows 10. :\ Google and Microsoft seem to agree with you, but I totally don't get it! If the website doesn't specify a style, my browser should fall back to a design that matches my OS, not whatever the browser developer thought was pretty! And if Windows is coming back and telling the browser to use Windows 98 styled button…

> The underlying problem is Windows suggesting Windows 98 styled buttons

I'm almost positive that Firefox doesn't use OS-native controls; they've specifically styled their controls to look the way they do, so yes, this is a Firefox problem, not a Windows problem.

Re: Firefox 76

#80

i just want to say, Firefox is seriously fast now, while Chrome continues to get slower [1]. my 10M datapoint uPlot benchmark runs in half the time, for both pure js (fake data gen) and canvas workloads (chart rendering). check out the console in [2]. however, i'm still waiting for the performance assessment in devtools to improve so i can get an easy summary as i can in Chrome. also, better default form input stylin…

> also, better default form input styling would be nice. it's so...Windows 98....but i'm on Windows 10. :\ Google and Microsoft seem to agree with you, but I totally don't get it! If the website doesn't specify a style, my browser should fall back to a design that matches my OS, not whatever the browser developer thought was pretty! And if Windows is coming back and telling the browser to use Windows 98 styled button…

> The underlying problem is Windows suggesting Windows 98 styled buttons. Microsoft should fix Windows.

i think that's the canned WONTFIX response for every bugzilla issue ever closed about it in the past, what, 7 years?

Post reply on HN