Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 77

mozilla.org

Post reply on HN
Print view View original

61–70 of 167 posts

Re: Firefox 77

#61

Post by vmateixeira »

jfk13 wrote: post #41
vmateixeira wrote: post #26

So... what kind of nonsense do I need to disable in about:config this time?

What a pointless question; how can any of us know what your individual preferences are like? Mozilla aims to ship a default configuration that works well for a large number of users. Of course there'll be people -- like yourself, apparently -- who'd prefer some things to be configured differently, but what you'd like changed is entirely up to you. Maybe you should be grateful Firefox offers (quite a lot of) customisa…

They don't need to know what my individual preferences are, actually, I would be glad if they don't try to "find them out".

Are you sure they're trying to ship what works best for most people? I've not read that anywhere. If they really wanted people to have a choice, they wouldn't be adding configurations that can't be switched on/off through they're preferences menu - like for example, that crazy bar they just added a couple of releases ago - oh.. and which apparently you are not allowed to switch off no more, not even through about:config, according to sibling comment. Also, they have a track record of breaking old configuration options quite often through updates.

I am grateful by what they offer - just not sure they're not sneakily changing course, similar to what chrome did.

Re: Firefox 77

#62

Post by [deleted] »

BitwiseFool wrote: post #58
msl wrote: post #49

Earlier quoted context omitted.

Oh, don't worry: more options have been removed again: setting browser.urlbar.update1 = false no longer gives you back the old, unintrusive urlbar behavior. Mozilla UX people have once again shown that they know best and you won't need to worry about getting a bad user experience just because you mistakenly thought you liked it. Edit: Changed 'disabled' to 'removed' in the first sentence, as it's probably clearer.

I've been googling for the last 20 minutes trying to figure out how to re-disable this. Ugh, I can't stand it.

[deleted]

Re: Firefox 77

#63

Post by nothis »

theandrewbailey wrote: post #45

Firefox 77 includes AV1 image format[0] support! You'll need to set image.avif.enabled = true in about:config. [0] https://aomediacodec.github.io/av1-avif/

Haven't been following this, is there any major site where this makes an impact? Youtube?

Re: Firefox 77

#64

Post by SamuelAdams »

msl wrote: post #49
vmateixeira wrote: post #26

So... what kind of nonsense do I need to disable in about:config this time?

Oh, don't worry: more options have been removed again: setting browser.urlbar.update1 = false no longer gives you back the old, unintrusive urlbar behavior. Mozilla UX people have once again shown that they know best and you won't need to worry about getting a bad user experience just because you mistakenly thought you liked it. Edit: Changed 'disabled' to 'removed' in the first sentence, as it's probably clearer.

So the only alternatives to fixing this is either switching to an LTS release or changing browsers completely? Is there an extension that fixes this?

Re: Firefox 77

#65

Post by huhtenberg »

BitwiseFool wrote: post #58
msl wrote: post #49

Earlier quoted context omitted.

Oh, don't worry: more options have been removed again: setting browser.urlbar.update1 = false no longer gives you back the old, unintrusive urlbar behavior. Mozilla UX people have once again shown that they know best and you won't need to worry about getting a bad user experience just because you mistakenly thought you liked it. Edit: Changed 'disabled' to 'removed' in the first sentence, as it's probably clearer.

I've been googling for the last 20 minutes trying to figure out how to re-disable this. Ugh, I can't stand it.

While you can't disable it, but you can still restyle it.

https://www.ghacks.net/2020/04/08/how-to-restore-the-old-fir...

Re: Firefox 77

#66

Post by zozbot234 »

Wowfunhappy wrote: post #54

And now my address bar expands on click, because browser.urlbar.update1 was removed from about:config. I knew this day was coming, but I'm still not happy it's here. The movement is distracting, and the alignment of the bar's expanded state is terrible. There's a reason most graphic design follows a grid system. We need a way to turn this off. I realize the old about:config flag was tied to a legacy code pathway, but…

AIUI, you can set the amount of items shown to 0 in about:config, and have what amounts to a non-expanding URL bar. It's not perfect, but it's a viable workaround.

Re: Firefox 77

#67

Post by ekianjo »

IanOzsvald wrote: post #33
okasaki wrote: post #25

Earlier quoted context omitted.

The $500M per year they get from Google isn't enough to pay the bills?

Developing more than one revenue stream is likely to be a more resilient strategy than hoping that Google is happy to keep paying a competitor browser to stay in business

Ads this way is not a sustainable revenue strategy, it's pocket money at best.

Re: Firefox 77

#68

Post by ivanfon »

NullPrefix wrote: post #55
appleiigs wrote: post #21

Earlier quoted context omitted.

I was curious about that too. I wasn't sure if it was targeted ads or a news aggregator. I think it's more of a news aggregator. From the Firefox New Tab FAQ ( https://help.getpocket.com/article/1142-firefox-new-tab-reco... ) > Are these stories personalized to me? For the most part, no. Most recommendations on your new tab come from a general list of the best of stories on the web. > Pocket occasionally partners wit…

>Are these stories personalized to me? For the most part, no. If they wouldn't be personalized, the answer would be no, instead of "for the most part, no". Lawyer speak.

The bottom of the page says it was updated today, now it says this:

> Are these stories personalized to me?

> For the most part, no. Most recommendations on your new tab come from a general list of the best of stories on the web. But Pocket is actively exploring ways to deliver personalized recommendations in a way that vigorously protects users’ privacy. Importantly, neither Mozilla nor Pocket ever receives a copy of your browser history. When personalization does occur, recommendations rely on a process of story sorting and filtering that happens locally in your personal copy of Firefox.

Re: Firefox 77

#69

Post by CaioAlonso »

SamuelAdams wrote: post #64
msl wrote: post #49

Earlier quoted context omitted.

Oh, don't worry: more options have been removed again: setting browser.urlbar.update1 = false no longer gives you back the old, unintrusive urlbar behavior. Mozilla UX people have once again shown that they know best and you won't need to worry about getting a bad user experience just because you mistakenly thought you liked it. Edit: Changed 'disabled' to 'removed' in the first sentence, as it's probably clearer.

So the only alternatives to fixing this is either switching to an LTS release or changing browsers completely? Is there an extension that fixes this?

Time to fork, I guess.

Re: Firefox 77

#70

Post by wtallis »

zozbot234 wrote: post #66
Wowfunhappy wrote: post #54

And now my address bar expands on click, because browser.urlbar.update1 was removed from about:config. I knew this day was coming, but I'm still not happy it's here. The movement is distracting, and the alignment of the bar's expanded state is terrible. There's a reason most graphic design follows a grid system. We need a way to turn this off. I realize the old about:config flag was tied to a legacy code pathway, but…

AIUI, you can set the amount of items shown to 0 in about:config, and have what amounts to a non-expanding URL bar. It's not perfect, but it's a viable workaround.

That sounds like you're talking about the dropdown menu that shows up below the URL bar, but the problem is the URL bar itself expands outside of its bounding box when it gets focus.
Post reply on HN