Firefox 2.0 RC2 Review

segphault writes "Ars Technica has a comprehensive review of Firefox 2.0 RC2. It includes screenshot comparisons that illuminate the user interface changes that have transpired since the second beta, and it examines the similarities between the browser tab implementation from Internet Explorer 7 and the new tab management features in RC2. From the article: 'If RC2 is any indication, Firefox 2.0 is an incremental improvement of the 1.5.x series with performance improvements and a handful of relatively useful features. Based on my own experience, I consider it stable enough for regular use, but I endorse caution for users that rely on a lot of extensions, as most extensions aren't yet compatible with Firefox 2.0.'"

Comments

Almost ready..

[Anonymous Coward]

After upgrading to V2 RC2, its working pretty good so far. Session restore is pretty handy (now I can install new extensions, restart the browser and start from whereever I had left), and tab management is pretty good too.

Though there are some bugs - esp the toolbar customization needs to be looked at. My V1.5 toolbar customization is not sitting well with RC2 - esp the Search Engine. Its hogging all the screen from left to right, and I had to move it to its own bar (previously, it was sitting with Google Toolbar).

And of course, better memory management was a welcome change.

All extensions except on worked fine (had to disable extension compatibility check for Greasemonkey, and it worked perfectly fine).

"most extensions"? FYI !

[arielCo]

Well, I use a lot of invasive extensions, and I only lost Session Manager, which is unsurprising since Fx now includes a similar feature and they would probably step on each others' toes. Survivors:

• Adblock Plus
• Video Downloader
• Inspect this
• IE Tab
• IE View Lite
• JS View
• EditCSS
• GMarks
• Google Notebook
• Sage RSS Reader

All in all, I agree that this is mostly an incremental upgrade, and it is somewhat faster, but I'm not sure it deserves the new major version. Several tiny UI bugs didn't get fixed.

Improvements for developers, too

[Black Acid]

Probably the most interesting features to programmers are the addition of the SQLite engine, and significant JavaScript enhancements heavily borrowed from Perl and Python. You can use generators (yield statement), Pythonic iterators, array comprehensions, and what the Mozilla people call "destructuring assignment". Some examples from the article for the curious:

/* Destructuring assignment example - swap two values */
[a, b] = [b, a];
 
/* You can return multiple values from functions now */
function f() { return [1, 2, 3]; }
var [a, , b] = f();
document.write ("A is " + a + " B is " + b + "<BR>\n");
 
/* Easier fibonacci sequences with generators */
function fib() {
  var i = 0, j = 1;
  while (true) {
    yield i;
    var t = i; i = j; j += t;
  }
}
 
/* Array comprehensions */
var evens = [i for (i in range(0, 21)) if (i % 2 == 0)];
 
/* New scoping semantics with 'let' expression/definition/declaration */
if (x > y)
{
  let const k = 37;
  let gamma : int = 12.7 + k;
  let i = 10;
  let function f(n) { return (n/3)+k; }
  return f(gamma) + f(i);
}

Good stuff.

Re:Is the big fat memory leak fixed?

[Kelson]

Yes and no.

Because there is no big fat memory leak. There are a whole bunch of little ones that add up. They've fixed a lot of them. They fixed a bunch of 'em in the 1.5.0.x series, and a bunch more in 2.0.

I doubt they've got everything, but 2.0 should have less of a memory problem than 1.5.

Re:Why ActiveX?

[nmb3000]

ActiveX is a Microsoft technology. Even Microsoft is trying to get away for the security holes they've created with that.

ActiveX is just an implementation of OLE and COM via the Internet Explorer browser. Anyone is able to write an interface that supports ActiveX controls. The idea that they are inherently insecure is an oft-proclaimed falsehood on Slashdot. IE's implementation has had problems, but that's not the same thing as the technology behind it.

ActiveX : Internet Explorer :: Extensions : Firefox

It all comes down to implementation of the interactive extension to the browser.

Sometimes, security means not implementing something if it cannot be implemented securely.

That is true enough, although the problem is usually between the chair and keyboard. The biggest problem with ActiveX, and the way it got it's bad reputation is users who click 'Yes' to everything. Give Firefox enough market share and it will become profitable for these malware authors to write extensions that screw a computer/browser the same way ActiveX can.

useful tip

[vivek7006]

I found a really useful tip from the article

Unfortunately, the green arrow button is difficult to remove from URL bar, but it can be accomplished by hitting about:config and tweaking the browser.urlbar.hideGoButton, changing it to "true."

Re:extensions and themes

[J053]

To make your 1.5 extensions and themes work:

1. Download the .xpi file
2. Unpack it (it's a ZIP file, really) into a directory
3. Edit the install.rdf file - find the line with "maxVersion:" and change it to (for example) "3.*"
4. Replace the install.rdf in the .xpi ZIPfile with your modified one
5. Install the extension/theme: in Firefox, browse to "file:///wherever-you-put-it/whatever.xpi"
                                                                in Thunderbird, use the Installer

I have yet to see an extension for 1.5.x that didn't work with 2.x after doing this

still has UI consistency/key command problems

[SuperBanana]

I reported this bug years ago and was told "probably won't happen until 2.0" and the bug was promptly closed/ignored:

In most modern operating systems, lists in dialog boxes can have a range of items selected by holding down shift, and individual items flipped on/off with a modifier key that varies slightly; in OS X, it's the apple/command key. Open up the cookies box, a place where selecting lots of items would be REALLY handy (ie, deleting all the crap cookies that will expire in "2046"), and try selecting multiple cookies. Bzzzzt, no go. And guess what? In pre-1.5 versions, you COULD do this, so it really WAS a bug/feature delete with 1.5. Now, select one cookie and hit the delete key. NOTHING HAPPENS. Why the hell not?

If you have partially typed anything in the URL bar and hit tab, half the time you aren't taken to the next text box in the browser window. Similar behavior happens elsewhere, only on a page.

It gets worse: just like older versions of 1.0/1.5, the current release candidate suffers from "keyboard-go-dead-itis." I've had to close Firefox FOUR times today because I could no longer enter text ANYWHERE. Not in forms, not in the URL bar, not in the search bar. Command keys (ie, apple-T for new tab) stopped working as well (1.5 still does this, though now usually only when Flash is on the page. Why Firefox allows flash to intercept command keystrokes is beyond me.)

Oh, and I still haven't figured out how to do the resume-where-you-left-off bit, despite having poured through the prefs pages several times.

Nightly Tester Tools

[Noksagt]

If you're too lazy to bump the maxversion of your favorite extensions, you can use the Nightly Tester Tools to fore the app into thinking an extension is compatible.

Re:Firefox 2 fixes the most common leaks

[bunratty]

It appears that the more common leaks are fixed in Firefox 2.

Re:Tab changes suck!

[MacJedi]

What about one global close widget?

You can do it. The parent poster had an incomplete list:

0 - only the active tab has the close widget
1 - the usual look (close widgets on each tab)
2 - no close widgets.
3 - global close widget (at far right)

SQLite enables new extensions like Zotero

[Augustus De Morgan]

Firefox 2 includes a critical new underlying database engine--SQLite--which enables new kinds of extensions, such as the free, open-source citation manager and digital research tool Zotero.