Are any of these fixes being backported to 56.x? I am not ready to upgrade to 57+ yet.
Offtopic: I get the feeling a fair few HN readers don't keep their browsers up to date for whatever reason. It's troubling, seeing as this is a very technical and presumably security-conscious audience.
58 is the fixed version.
>I get the feeling a fair few HN readers don't keep their browsers up to date for whatever reason.
That's because 57 was a complete dumpster fire. It broke all the add ons. Little wonder people would not update. I was a happy FF user for years. My solution was to dump FF and move on, but I know there are still a lot of people clinging to 56/52 like debris from a shipwreck. Anyone who points this out is granted invisibility powers on HN, so I can see how you would be unaware of this.
FTA: This issue did not affect Firefox for Android or Firefox 52 ESR.
> That's because 57 was a complete dumpster fire.
I disagree.
> It broke all the add ons.
Yes, it did. They probably should've made 56 an ESR.
> Anyone who points this out is granted invisibility powers on HN, so I can see how you would be unaware of this.
They must not be doing a very good job, since I've seen the death of long-loved addons mentioned in every Firefox thread on HN for years.
Clinging to 56 is ... well, it's your decision to use what software you want, that's what free software is all about, but since half the point of the changes in 57 was improved security architecture, clinging to 56 and expecting fixes for security bugs seems ill-advised.
Customer controlled environment, where the only browsers are IE 11 and FF ESR, and having Chrome is considered security violation, because their IT cannot control it the same way.