User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/2.0 In pre-2.0 Firefox, I could go to a new URL by simply clicking the URL window, at which point it usually turned dark (as in selected text) and I could immediately type a new URL address. (Sometimes I had to click within the Firefox window first, but then the method would immediately work.) With Firefox 2.0, whenever I click in the URL window, regardless of previous activity, I have to backspace/delete every character before typing in a new URL. Do I have something set wrong? Can I correct it? This was a wonderful Firefox feature and I sorely miss it. Reproducible: Always Steps to Reproduce: 1. Go to some URL. 2. Click within the URL window to go to a second URL. 3. Or click within the main window, then click within the URL window. 4. (I have the standard default Firefox 2.0 installation, just installed from latest upgrade of Firefox 1.5.0.7?) Actual Results: Happens every time. Expected Results: In previous Firfox versions, I could click within the URL window, it would change color, and I could then type in a new URL (either whole or recalled from history). I'd like to get back this highly useful feature.

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1) Gecko/20061025 BonEcho/2.0 ID:2006102503 Works for me. Sure you don't have any extensions that are interfering with firefox? Try in safemode to see if this is the case http://kb.mozillazine.org/Safe_mode

That (and your user-agent string, half 2.0 and half 1.5.0.7) are symptoms of a broken install of 2.0, when 1.5.x was still running and the installer didn't manage to shut it down, so some files weren't overwritten. Your best bet is to delete the whole Firefox directory from Program Files (or wherever you have it) and install again (after making sure in Task Manager that there are no firefox.exe processes running, and no other users have it running). *** This bug has been marked as a duplicate of 357922 ***