From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.7) Gecko/20011221 BuildID: 2001122106 In all other versions of Netscape, Explorer, OmniWeb etc. and in the Linux Mozilla I can type a URL into the location bar and hit return to have the browser open that URL. In the MacOS X version (and this occurred in the 9.6 build as well) I can type in that window, but there is no obvious way to actually go to that URL. I have to use the Open Location... dialog, which is a pain. I assume this is a bug, and not a planned user interface feature. Reproducible: Always Steps to Reproduce: 1. Open Mozilla 2. Type a URL into the location bar and hit "return" 3. Observe nothing happening. Actual Results: Nothing at all. Expected Results: Should have opened the entered URL. G4-733 Desktop system MacOS 10.1

wfm with win2k build 20011221.. Reporter: Have you installed Mozilla in a fresh directory (and not over an older build ?) Can you try to create a new profile with "mozilla -profilemanager" ?

Sounds like bug 90337 .

Reporter, please apply what Mattias suggested. Report here the results.

One has to remove Mozilla folder from the user Library folder to create a new profile on OS X.... no profile manager exist (for the most part) But a report in the OS X newsgroup reported this exact same problem and has removed the current profile and restarted mozilla same problem... also using .9.7... and it has been metioned on a few other mac sites. From the NG (recorded from JavaScript Console): "Error: uncaught exception: [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIRDFService.GetDataSource]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: chrome://navigator/content/sessionHistoryUI.js :: addToUrlbarHistory :: line 168" data: no]" This isn't an issue on the trunk of os x (2001122105 build)

Now I'm sure this is bug 90337. (See comments #22, #31, #32, and other duped bugs)

I did install in a fresh directory (i.e. threw out the old one before moving the new Mozilla directory from the mounted disk image) HOWEVER, I made a new profile from scratch, and the problem went away. This sounds like a major clue. This does sound like bug 90337. I'm curious why I didn't turn that up when I was searching for similar bugs...

*** This bug has been marked as a duplicate of 90337 ***