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

Firefox 86.0

mozilla.org

Post reply on HN
Print view View original

161–170 of 183 posts

Re: Firefox 86.0

#161

Post by marcosdumay »

AshamedCaptain wrote: post #110
marcosdumay wrote: post #83

Earlier quoted context omitted.

And have it all reverted at random because well "there seems to be along time since you last used Firefox, do you want to lose all your configurations? Yes. Later."

Each time I see that prompt I have to pause and consider the otherwise wacky theory that there evil forces trying to cripple Mozilla from the inside. Why. Just why.

I dunno. Software often have very unintuitive features, like the problem of closing with CTRL-Q on Linux, that looks like a "damn, why did they put it there on the first place", but actually is something GTK does if you follow the guidelines (what goes to show that most software doesn't follow them).

My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough.

Re: Firefox 86.0

#162

Post by extra88 »

alecmg wrote: post #90

Found a random improvement: Kraken 1.1 benchmark runs faster now. Improved from roughly 760 to 700ms on my 5800X. Still ways to go to reach Chrome at 560ms

Running that benchmark on my Mac (Catalina), I see a comparable difference between Firefox and Chrome but Safari (14.0.3) is ~10% faster than Chrome. This wasn't with any care taken to create a controlled environment and my Firefox had plenty of tabs open.

Re: Firefox 86.0

#163

Post by rablackburn »

clairity wrote: post #70
megous wrote: post #8

I wonder if the web engine development pretty much stopped, or developer notes are just less detailed over the last year or so. Those are a shadow of the former self, certainly.

it’s particularly aggravating that form fields have been largely stagnant over the past 20 years. so much repetitive development happens around forms (validations or date/time pickers, for instance) and yet very little effort goes into improving them.

I’ve noticed this too. I’ve found myself iterating on a nice extended form control library where I try to extend the native inputs and forms in the most minimal, yet complete, way I can.

There are actually a lot of nice improvements being discussed in the CSS level 4 specs, but some of the issues are last tagged as updated in 2012...

But basically we just need a consistent value interface (two-way data binding), and a more finely-grained validation/state lifecycle where we can plug in our own custom validation functions.

Colleagues and I always joke that every web developer gets the idea to write a form library at some point, and suffering through trying to implement it is the only way to dissuade them of the idea. Now the joke is on me as I’ve come full circle back to writing one.

I’ve spent so much time on it now I’ve been considering reaching out to help contribute to the spec. But I have no idea how receptive the working group is. This may just become my eternal project, there’s always more edge cases to find.

Re: Firefox 86.0

#164

Post by forgotmypw17 »

marcosdumay wrote: post #161
AshamedCaptain wrote: post #110

Earlier quoted context omitted.

Each time I see that prompt I have to pause and consider the otherwise wacky theory that there evil forces trying to cripple Mozilla from the inside. Why. Just why.

I dunno. Software often have very unintuitive features, like the problem of closing with CTRL-Q on Linux, that looks like a "damn, why did they put it there on the first place", but actually is something GTK does if you follow the guidelines (what goes to show that most software doesn't follow them). My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, s…

>My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough.

I think this is actually a good feature, one of the few introductions which I think if worthwhile, even if the implementation is a bit lacking.

You have to balance the user being able to see the message with not annoying them, and it's not difficult to achieve.

Configuration bloat is a real problem in most applications which allow third-party extensions, and I've seen some stunning examples of extensions bloat on some people's computers, Chrome users included. On the other hand, when I question it, they tell me, "I use all those!"

This article I came across here on HN really enlightened me: https://www.asktog.com/columns/000maxscrns.html

Re: Firefox 86.0

#165

Post by pabpab »

firefox 86 gets stuck on cntrl p (says preparing preview and nothing happens)

worked perfectly before, again a case of 'if it works -----'

the `print.tab_modal.enabled` preference to `false` fix described below helped

Re: Firefox 86.0

#166

Post by pabpab »

jwatt wrote: post #74
iso1631 wrote: post #53

Earlier quoted context omitted.

I'm on Firefox 84, pressing file/print or ctrl-p brings up a preview window on the left, printer selection on the right.

The new print interface has been progressively released to a subset of users over multiple releases. It's only gone to 100% of users as of Firefox 86.

it does not work here the `print.tab_modal.enabled` preference to `false´ fix described below helped

Re: Firefox 86.0

#167

Post by pabpab »

jwatt wrote: post #81
callmeal wrote: post #66

Earlier quoted context omitted.

For those of us that prefer the OS print dialog, how can we stop this madness?

We intend to add a keyboard shortcut for this[1]. In the meantime you can revert to the old printing interface by setting the `print.tab_modal.enabled` preference to `false` via the page `about:config`. In a few releases time, after we've finished integrating user feedback and polishing rough edges, we intend to remove that preference though. 1. https://bugzilla.mozilla.org/show_bug.cgi?id=1667950

thanks, this helped , things went back to 'working'

Re: Firefox 86.0

#168

Post by benhurmarcel »

callmeal wrote: post #66
matsemann wrote: post #23

Wow, Ctrl+P has now started to open the proper print-interface with a preview! I've helped loads of people over the years complaining about printing in Fx vs Chrome. It used to be so in Fx that selecting Print from the menu opened an interface for printing (ala Chrome), but pressing Ctrl+P just opened standard OS print dialog. So power users never saw the nice print preview.

For those of us that prefer the OS print dialog, how can we stop this madness?

Reminds me of that: https://xkcd.com/1172/

Re: Firefox 86.0

#169

Post by marcosdumay »

forgotmypw17 wrote: post #164
marcosdumay wrote: post #161

Earlier quoted context omitted.

I dunno. Software often have very unintuitive features, like the problem of closing with CTRL-Q on Linux, that looks like a "damn, why did they put it there on the first place", but actually is something GTK does if you follow the guidelines (what goes to show that most software doesn't follow them). My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, s…

>My bet is that they were receiving complaints of Firefox breaking due to bad migration of settings between versions, so instead of fixing the migrations, they decided that this user-hostile anti-feature was good enough. I think this is actually a good feature, one of the few introductions which I think if worthwhile, even if the implementation is a bit lacking. You have to balance the user being able to see the mess…

Hum... Keep in mind that there is no option to not erase your configurations. And that "configurations" has a very bread sense, including everything from about:config settings, themes, extensions, history, cache, cookies, saved passwords, and even for a short period including bookmarks (thankfully that one they stopped erasing). And, by the way, Firefox will revert from a backup if you are logged in into an account, what is probably the reason the devs didn't nuke this by themselves, but also leaves plenty of room for conspiracy theories and user enragement.

Having a button somewhere where the user can go and reset those things is ok. But keeping pestering them until they click on the button is really not.

Re: Firefox 86.0

#170

Post by folknor »

pentagrama wrote: post #60

Not totally related, but someone know if exist an RSS feed to follow the stable Firefox releases? Can't find it on this page. This Firefox changelogs are awesome to know big improvements and new features on a surface level. For Chrome I didn't find a proper way to follow the releases even if it has some RSS feeds, I follow the RSS feed of Chrome Releases blog [1] with a tag filter [2] but can't exclude the several po…

https://hg.mozilla.org/mozilla-unified/tags https://hg.mozilla.org/mozilla-unified/atom-tags https://hg.mozilla.org/mozilla-unified/rss-tags

And here's my lua script that uses notify-send to notify me of new releases: https://gist.github.com/folknor/32f703b270c6ad72bc12d98feb2f... I modified it slightly before posting it here, but it's mostly useless unless you're me :-D Because when I write shell scripts (which I always do in lua), I always use my fork of luash (from my github), and I don't imagine anyone else has it. It's easy enough to rewrite the script to not require it, though. Also, the other obscure dependency it uses is lua2xml, which is notoriously unreliable, but I still use it in all my shell scripts that interact with XML.

Post reply on HN