It looks like it’s time for another sneak peek at an upcoming Firefox upgrade …
You may have noticed that the usual suspects are already reporting that a new stable version of the Mozilla Firefox browser has been released by Mozilla. While it is true that a build has been moved to the release server, we have seen in the past that this version can get replaced in last minute if the build does not pass the company’s quality controls.
There sure have been a lot of stories like this lately; it seems like for every interface “upgrade,” there’s a program out there somewhere that will help you undo the upgrade.
If you have been following the recent development of the Firefox web browser, and in particular Mozilla’s plans with the next upcoming versions, you know that there will be lots of – good – change coming to the browser. From excellent features like click to play, a new Firefox design, a Metro version for Windows 8, Silent Updates, and many cool features for Firefox 13 (which not all may make it into that version).
Firefox seems to be doing a good job at addressing its former reputation as a memory hog …
When you ask computer users about memory intensive browsers, you likely hear Firefox being mentioned more often than Google’s browser, Opera or even Internet Explorer. It is rather interesting that much of this comes from a time when Firefox’s memory usage was indeed not the best. When you look at more recent memory tests, you will notice that Firefox more often than not beats the competition in this field.
Here are some extremely helpful tricks that can be used to improve both the security and privacy of the Firefox browser …
Firefox is awesome! No, seriously, it is. Why? Countless add-ons, its open source, has many tweaks and most of all: the browser respects your privacy and dedicates a lot of effort to keeping the browser secure. In this post, we will be talking about both the security and privacy side of the Firefox browser. First we will discuss general Firefox settings, then go “under the hood” and finally, recommend some extensions. The current version of Firefox is 11.0. I cannot guarantee all these tweaks will work in future versions.
I’m so old, that I remember a time when Netscape Navigator used to be the hottest browser around …
Steven J. Vaughan-Nichols questioned whether the Mozilla Firefox web browser has a future in the web browsing market in a new commentary on ZDnet yesterday. Lets take a look at the points that he makes to better understand the argument.
This makes good sense; many earlier versions of Java were riddled with security holes …
Running old plugins in your web browser is bad, as it opens the door for all sorts of mayhem. This includes exploits that target known vulnerabilities in those versions, or stability and compatibility issues that you may experience as a result of that. While users are to blame for that, it is also something that browser vendors have not really taken care of.
Here’s a useful summary of the new Firefox Silent Updates feature …
By now you must have heard about the silent update feature that Mozilla is currently working on for the Firefox web browser. I first covered silent updates back in October of 2010 when Mozilla started to announce plans to integrate a better updating mechanism into the browser.
Wow. This is kind of unusual; a spokesperson for Mozilla is recommending an alternative for Firefox 3.6 users who aren’t interested in upgrading …
If you are a Firefox 3.6 user you know by now that support for that branch of the web browser will end on April 24, 2012. As it stands now, Firefox 3.6.28, released on March 14, is likely the last version of Firefox 3.6. Mozilla will not update the version of the browser again unless a major security or stability issue forces them to.
I sure hope that Firefox’s built-in PDF reader turns out better than Chrome’s built-in PDF reader; in my book, Chrome’s PDF reader leaves a bit to be desired when compared to Adobe Reader.
Browser plugins may soon become a dying form of adding functionality to web browsers. We are already seeing first signs of that, for instance with Chrome’s built-in pdf reader, or the drive towards HTML5 video and media in general. The biggest issue with plugins, besides compatibility, is security, and here the need to keep plugins up to date to avoid attacks that exploit known vulnerabilities that have already been fixed in the latest plugin versions.
