When you hover over a link, the status bar tells you where it will take you.

This is important (especially for security) — important enough that they’ve moved the functionality elsewhere…but in a broken manner. They’ve put it into the location bar — you know, the field where you type in a URL, or look to see where you are.

The problem is that there isn’t room in the location bar to show the full URL of a hovered link except for very short links. The status bar has the entire width of the browser. The location bar has to share that space with the navigation buttons, the search box, the feedback button (during the beta), any custom toolbar buttons, the site name on secure websites, etc.

Just about every link I hover over ends up with critical information cut off in the “…” between the start of the hostname and the parameters at the end. That’s almost useless. (Almost, because at least the hostname is visibla, but it would help to see the page name as well.)

Displaying the target URL in some way is core functionality for a web browser, and you shouldn’t remove or break core functionality. In some ways this is worse than the proposal a few years ago to remove “View Source,” because that at least isn’t core functionality for a browser (though it is core functionality for the web, because it encourages people to explore and tinker and learn how to make their own websites — which is exactly why that was put back in). It’s crazy that I need to install an add-on to get back something as basic as a working preview for links.

Within days, they released an update. I couldn’t imagine what they might have missed in all the beta testing. Katie wondered if the beta testers hadn’t been testing the limits.

You want to know what convinced Mozilla to issue an update so quickly?

Farmville.

Apparently Firefox was detecting Farmville as frozen and closing it. It turns out that on many computers, Farmville regularly freezes up the browser for longer than 10 seconds, and its players just deal with it and wait for it to come back. Mozilla decided that the simplest thing to do would be to increase the time limit.

What this tells me is that the type of person willing to beta-test a web browser these days is not likely to be playing Farmville — or if they are, it’s likely to be on a bleeding-edge computer that can handle it without 10-second freezes.

In more practical terms: Mozilla needs to convince a wider variety of users to help test their software!

Update: Apparently that’s not it, since I had both the console and script panels disabled as described in that article. Oh, well.

It starts at 10:00 AM Pacific Daylight Saving Time (the Mozilla offices are in Mountain View, California), i.e. 17:00 UTC. You can use a time zone converter to figure out your what time that is in your own time zone.

Only full downloads count, so if you’ve been using one of the release candidates and want your download to be counted for the record, you’ll have to go to the website instead of just using auto-update. Edit: The Download Day page is swamped — just head to Mozilla.com for now.

And yes, Firefox 3 is good. I’ve been using the betas and release candidates for several months, and it’s a huge improvement over version 2!

Neither browser has announced a definite release date (though Mozilla has stated Firefox 3 will launch in “late June”), but both are in the final stages. Update: Mozilla has announced a release date of June 17.

Update 2: Opera wins with a June 12 release.

• Read about Opera 9.5 RC1
• Read about Firefox 3 RC2