Update Firefox: Mozilla just patched three hijack-me holes and a bunch of other flaws

Mozilla has emitted security updates for Firefox to address eight CVE-listed security flaws, five of them considered to be high-risk vulnerabilities. The patches, present in Firefox 77, should be downloaded and installed automatically for most users, so if you haven't closed out and relaunched your browser in a while, now …

[Gene Cash]

Hahaha, Firefox 77?! I'm still on 43 because they dropped ALSA sound support, fine-grain cookie control, and a whole bunch of other useful shit.

I once met a Mozilla "developer" - I said "oh really? which features are you working on removing from Firefox now?"

For some reason, he stopped talking to me. Darn.

[robidy]

Isn't Firefox open source? You're being rather unkind to someone giving something back.

[Anonymous Coward]

He stopped talking to you. You, with this lovely, insecure, sneering attitude towards volunteer developers.

I bet there's plenty of people you've met who stopped talking to you.

[Charlie Clark]

We get it: you're happier running an older, less secure version because the newer versions have less features. I think we all do this to one degree or another for various bits of software. And, while I object, to the dumbing down of the UI in Firefox, I do understand the reasons they gave for dropping the older architecture, which is demonstrably safer because it is more restrictive. Fortunately, I didn't have any extensions that were permanently broken. Firefox is now faster and includes some features that were previously only available via extensions.

[Anonymous Coward]

I'd be happy

if they fixed printing so that you'd get more than just the first page when you try to print a web page.

[robidy]

Re: I'd be happy

Doesn't that depend on the CSS of the site. The copy a page as an image works fine for me....it's the icon at the end of the address bar...print as a normal image if needed.

[Charlie Clark]

Re: I'd be happy

Printing multiple pages works fine here. Good printing of website pages is almost always dependent upon the website developers providing reasonable CSS for the purpose.

[sev.monster]

Re: I'd be happy

With the advent of React, Angular, and other such webmonkey magic, it seems the idea of a single, easily-parsed and printer friendly page containing all relevant information has fallen by the wayside to make way for ajax and lazy-loading everything.

Printing aside, I always love it when whole sites don't load because I disable JavaScript and the thing is served as a "webapp". Unless I have to use it the tab is closed at that point.

[Charlie Clark]

Re: I'd be happy

Too, true. SPA websites kill performance. But they can still have usable print stylesheets, if the developers bother to think, or, more likely if the framework du jour has them.

[paulf]

Re: I'd be happy

Disagree to some extent. There are many pages that print fine in other browsers but Firefox still can't cope with. One example is the radio program playlists on the BBC website, example:

Pete Tong 2020-04-10

Prints fine in IE 11 on Win 7, but still fails to print properly on the latest Firefox ESR release (68.9).

When IE is better in a "Just works" kinda way, you might want to consider if you've got something fundamentally wrong. Printing in FF has been a bin fire for years and it's not because it's not possible, it's because it's not possible in Firefox.

[Nick Ryan]

Re: I'd be happy

By way of printing that looks quite reasonable and no less messed up than most other web page print attempts. (FF 76.0.1)

[Anonymous Coward]

DNS over HTTPS

In what one assumes is a response to ElReg's comments, Firefox released 77.0.1 whose sole change is "Disabled automatic selection of DNS over HTTPS providers during a test to enable wider deployment in a more controlled way."

[sev.monster]

Re: DNS over HTTPS

Beer? Do they really deserve it for undoing a poor decision they made? Or am I just being curmudgeonly?