Here is what is new in Firefox 67.0.2
Mozilla released Firefox 67.0.2 to the Stable channel on June 11, 2019. The new version of the Firefox web browser is already available and Firefox installations configured to check for updates automatically will pick up the new version eventually to download and install it.
Firefox users who don't want to wait for that to happen can run a manual check for updates with a click on Menu > Help > Check for Updates.
The new version is also available as a direct download on the Mozilla website.
Firefox 67.0.2
Firefox 67.0.2 is a bug fix release that addresses several issues in the browser. Here is the list of changes and improvements in the release:
- Fixed the JavaScript error "TypeError: data is null in PrivacyFilter.jsm" which could "significantly degrade sessionstore reliability and performance".
- Manual proxy setups may have seen multiple proxy authentication dialogs with requests to authenticate in Firefox 67.
- Persaon's MyCloud breaks if FIDO U2F is not Chrome's implementation.
- Fixed an issue in Firefox for Linux and Mac OS X that caused Firefox to display a "profile is to recent" notification to the user if Safe Mode was used prior to the launch.
- Fixed problems associated with installing and managing different languages in Firefox on Linux distribution systems.
- Fixed a tag copying problem in the Firefox developer tools.
- The custom homepage did not work correctly for users who configured Firefox to clear data on shutdown.
- Fixed a performance regression for eclipse RAP based application.
- Fixed a crash that affected Mac OS X 10.15.
- Fixed an issue that prevented the starting of two downloads in parallel.
Firefox users affected by any of the issues may want to consider upgrading to Firefox 67.0.2 immediately to fix the issue that they experience.
Interested users can check out the official release notes. These link each fixed issue to the bug report on Mozilla's bugtracking website which offers additional information on it.
The next major Firefox release, Firefox 68, is scheduled for a July 9, 2019 release.
Now You: Did you notice any of the issues in Firefox 67?
We need your help
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Previous Post: « Firefox 68: add-on release notes in add-ons manager
Next Post: A closer look at Firefox's Tracking Protection feature »
The Fugees – Ready Or Not https://www.youtube.com/watch?v=aIXyKmElvv8
Daily updates on the way [Editor: removed, please remain polite]
I’m still using 66.0.3. I use a policy to disable updates. You can just temporarily move the file out of the folder when you want to update FF.
You create a policies.json file and store that file into the ‘C:\Program Files\Mozilla Firefox\distribution’ folder. Create a ‘distribution’ folder in \Program Files\Mozilla Firefox\ folder and place that policies.json file into that folder with the following contents:
{
“policies”:
{
“DisableAppUpdate”: true
}
}
The formatting got lost in my previous post, that policy probably won’t work like that. You can go here to find policies to use in FF.
https://github.com/mozilla/policy-templates/blob/master/README.md
Amen to this. This saved my life! It was so annoying every day it prompts for updates with nag screens and ads.
What are you talking about? I have never seen these “ads” or nag screens. Maybe you should visit the setting page instead of blocking updates which contain security updates. Just saying…
Ummmm Why?
Dave, The Firefox installer will remove the distribution folder when updating next time. Make sure to update via command line using the /RemoveDistributionDir=false switch.
“Dave, The Firefox installer will remove the distribution folder when updating next time.”
I’m sorry, Dave. I’m afraid I can’t let you do that, Dave. This browser’s mission is too important for me to allow you to jeopardize it.
https://www.youtube.com/watch?v=UgkyrW2NiwM
BeWarned, not a problem as I have to move the policies.json file out of the folder to allow the update proccess run when I want it to.
I just recreate the folder and move the file back in when the update is finished.
Some obvious things not mentioned, and which are extremely obnoxious, is that user settings are obliterated and can’t be reset:
1.Although “ask where to download” is checked, files still go to the ‘Download’ folder and can’t be redirected,
2. Same for “Restore Session” – even when it’s designated “false” in the ‘about:config’ settings, Firefox still returns to previous webpages after crashed sessions. This is especially aggravating when a site ties up a user’s device or tries to load a virus.
Wiping out user settings during upgrades is bad enough, but not allowing them to be reset is even worse. It’s the kind of arrogant attitude and disrespect for users Apple is notorious for.
Using that version and it constantly crashes. Worst version yet. Hope 68 fixes the problem. It freezes constantly. I shut down manually. Several times a day. Super clean computer with no other issues. About to switch back to Edge or Chrome.
Did you try running Firefox in Safe Mode just to see if that resolves the issues?