Firefox 2.0 To Debut Tuesday
An anonymous reader writes "Firefox 2.0 for Tuesday, says the Seattle PI. They give a quick recap of some of the new features, and discuss the ongoing IE vs. Fox debate." From the article: "Version 2.0 also improves on the tabbed-windows interface that Mozilla innovated and that Microsoft introduced for the first time last week with IE7, its biggest upgrade since 2001. Analysts said IE7 is a significant improvement over its predecessor, but the big question is whether it will stem Firefox's growth at Microsoft's expense. Firefox's share of the browser market has grown to 9.8 percent of the U.S. market this month, from 2.9 percent in October 2004."
Its Sunday after all right now, so why not pray for FireFox? This is FireFox 2.0 Beta running on my Windows XP PC.
1. Starts without maximizing itself to the full PC screen area. Always leaves space available. In contrast SeaMonkey correctly occupies the full PC screen area when starting (but SeaMonkey makes me create a new profile except for once.). FF thinks its full screen according to its maximize/window button but is mistaken.
2. FF fails CSS rendering because it uses an antique CSS engine.
http://www.webstandards.org/action/acid2/
Those are my FF issues. What are yours?
Thanks,
Jim Burke
With the new spellchecker they will also be introducing a new attribute to the input tag: http://developer.mozilla.org/en/docs/Controlling_s pell_checking_in_HTML_forms
Is this a non-standard attribute? Are we going back to each browser adding stuff and hoping the other one stays relatively compatible? I'm not saying whether this is a good or a bad thing. I was just curious.
Besides having far better CSS support than Firefox 2.0, Konqueror also uses only a fraction of the resources. Opening the exact same sites in Firefox and Konqueror will often show a major difference between the two in terms of RAM usage.
For example, when I simultaneously open about 15 of the blogs and websites I read daily, top reports Firefox 2.0 rc3 as using 149 MB of virtual memory. Konqueror, on the other hand, uses a cool 28 MB for those exact same sites. Opera uses 31 MB. So as far as I can tell, Firefox is the lame duck when it comes to effective memory usage. This is with a build right from mozilla.org, without any additional extensions installed. I also disabled the cache for all three browsers, since I've heard that Firefox has a policy that leads to excessive memory usage.
A problem I have had with the Firefox 2.0 release candidates is crashes. This doesn't happen with Konqueror, or any other application I'm using, so I doubt it's faulty RAM. These crashes aren't easily reproducible, and I frankly don't have the time to bother debugging an application that I really don't use, and that crashes the few times I do try it out.