Here is what is new in Firefox 65.0.1
Mozilla released Firefox 65.0.1 to the browser's stable channel yesterday. The new release is a bug fix and security release and as such a recommended update for all stable users.
It is usually the case that Mozilla releases a smaller update after every major Firefox update (major in regards to the version increase) to address bugs and other issues.
Firefox 65.0.1 is such a release but it is also a security release which is not that common. Firefox users should get the update offered to them automatically when they run the browser and have not disabled automatic updates in Firefox using Enterprise policies.
Those who don't want to wait until it is there turn can select Menu > Help > About Firefox to download and install the new update right away. Firefox 65.0.1 is available as an offline installer as well.
Firefox 65.0.1 follows Firefox 65.0, a release that had to be halted on Windows for some time to address a compatibility issue with certain antivirus programs.
The official release notes list the following fixes:
- Improved playback of interactive Netflix content.
- Fixed an issue that caused delays when making WebRTC calls.
- Fixed problems with sizing video when making WebRTC calls.
- Addressed an issue where add-on recommendations would make a call to Mozilla's AMO website before the user hit the install button.
- Fixed an issue that prevented the Enter-key from working on certain password entry fields on Linux.
- Fixed a color management issue on Mac OS X devices.
- Addressed a looping CONNECT requests issue with WebSockets over HTTP/2 from behind a proxy server.
The new version of Firefox addresses several security issues next to that. You find the list of security issues fixed in the Firefox 65.0.1 release here.
The page lists three security issues that have all been rated with a severity of high, the second highest severity rating after critical.
Firefox for Android is also updated to incorporate the security fixes and the CONNECT bug fix.
Don’t know about anyone else, but the update seems to have broken a number of websites on my end. Do they even test shit before shoving it out?
If all your broken sites are https and if you use Avast, turn off its web shield.
Avast’s web shield is off, (Ran into that before and just never saw a reason to re-enable it.) Have gone back to version 65.0 and no problems with no other changes on my system.