Mozilla testing near-final Firefox 3.5
Mozilla is close to releasing of its near-final version of Firefox 3.5, but the updated browser wasn't quite ready in time for a planned day of widespread testing.
Earlier this month, Mozilla set Friday to be Firefox 3.5 RC1 Test Day. But RC1, the first release candidate designed to be more stable than the earlier Firefox beta versions, wasn't finished for the occasion.
"Even though RC1 hasn't been released yet, the test day will still go on with the latest nightlies (nightly builds of Firefox based on the latest source code) which are practically RC1 minus some minor uplifts," said Aakash Desai of Mozilla's quality assurance team on Thursday. Mozilla has set up the Litmus program to encourage broad testing of its software.
RC1 is expected in a few weeks, spokeswoman Melissa Shapiro said Friday, though one developer told CNET News he hoped it would arrive in less than two.
The new version of Firefox began as version 3.1, a modest update. But a gradually expanding feature list led Mozilla to rename it 3.5 and release it months later than had been planned initially. In the meantime, Microsoft released Internet Explorer 8, Apple released a beta of Safari 4, and Google has released a rolling series of upgrades to its new Chrome browser.
Among the changes compared with the current Firefox 3.0.x versions are the faster TraceMonkey engine for running Web sites' JavaScript programs; support for tags to describe audio and video content the way images have been available for years; the private browsing mode for leaving no traces on your computer while surfing; support for geolocation technology to let permitted applications know the user's location; built-in JSON (JavaScript Object Notation) technology for exchanging data between servers and browsers; and support for the Web Workers standard for letting a browser perform processing in the background without holding back a Web application's user interface.
Stephen Shankland writes about a wide range of technology and products, but has a particular focus on browsers and digital photography. He joined CNET News in 1998 and since then also has covered Google, Yahoo, servers, supercomputing, Linux and open-source software, and science. E-mail Stephen, or follow him on Twitter at http://www.twitter.com/stshank. 



I used Firefox 3.5 beta earlier today, runs fast, renders pages quickly with no trouble and runs every addon I use on a day to day basis.
The problem with addons is when you go overboard and, if you're complaining there are too many, I'm betting you went overboard with them.
By the way, both Chrome and IE are trying to get more addons, Firefox just happens to have the hard part already in place.
That's nowhere near true.
I've been updating Firefox from v3.0.0 and none of my extensions stopped working. (and i have lots of them)
Plus, it's the author of the extension that specifies whether his extension should stop working with a new minor release, although a minor release doesn't affect extensions, so it's the authors mistake not Firefox's.
it was supposed to be released it December
and BTW, 1812, do you think it's acceptable that a minor dot update to fix bugs or security holes breaks just about every theme or extension you have installed? I don't know of any other software that behaves this poorly, so why is that defensible?
It is the author of the extension/theme who has to check its compatibility. If the extension is not being regularly updated, it is the author's fault, not Mozilla's.
Wow, what a superfluous statement. Every single addon breaks? Not really, there are a few handful that break but I'm a risk taker and I have disabled addon compatibility checking. If any problem, occurs, I'll open up in safe mode and then permanently disable the culprit addon.
Remember that each extension has its own author that is usually not affiliated with Mozilla at all other than the fact that they upload their addon to a Mozilla site. It is not Mozilla's job to pester developers to update and test their code.
More tacky bloat, you mean.
The plugin developer is the one who sets the compatability. Some developers set it open so no check is done. Some set a "maximum" version for compatability. But you can override this check.
1. In your address bar, type "about:config" (remember, no quotes).
2. Once the configuration page loads, right click anywhere within the configuration options list and select "New" and then select "Boolean" from the choices given.
3. The next box that pops will ask you to "Enter the preference name". Enter: "extensions.checkCompatibility" (without quotes). Then click OK.
4. Another box will pop up asking you to choose the Boolean value. Select "False" and click OK. Your new statement should now appear in the list of configuration options.
5. Restart your browser and all your incompatible add-ons should mostly work.
Keemal
Try https://addons.mozilla.org/en-US/firefox/browse/type:2 for many many skins/themes to change the look of firefox. They are as easy to install/use as a plugin. They have compact, aero, holiday themed, etc.
E
IE is the least compatible browser out there. For my websites, I usually have to add extra code just to get the site working in IE.
Also, Firefox (version 3.0.10) is already the safest. I once wrote a test webpage just for fun in about 5 minutes that prevented the page from being closed. Every time I tried to close it in IE, Safari, and Chrome, it would just open a new window with the same webpage. But that script didn't work in Firefox. Go Firefox!
http://reviews.cnet.com/browsers/firefox-3/4864-3514_7-33087853.html?messageID=10022241&tag=commProfileMain;profileBot
I use the IE Tab add-on which automatically uses the embedded IE rendering engine for MHTML pages
I prefer unobtrusive features over a very slight speed difference any day.
HUGE memory usage is my primary concern with the new 3.5, can someone who has used it address this? Is this corrected. I like FF3 otherwise.
- by rshimizu12 June 7, 2009 11:40 PM PDT
- Firefox works great. I can view 99.99999% of all web pages without problems.
- Like this Reply to this comment
-
(37 Comments)