User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_2; en-us) AppleWebKit/525.13 (KHTML, like Gecko) Version/3.1 Safari/525.13 Build Identifier: head I've found a race condition where if Firefox 3 beta 5, and HEAD, pop up a login panel for a proxy-auth server before it opens the first browser window the menu bar doesn't get properly setup. Which is to say only the Firefox menu item gets populated and then others like Edit, View, History ... are missing. So far I've only seen this on the Macintosh. Reproducible: Always Steps to Reproduce: 1. Setup FF to use a proxy-auth server and a non-local startup page. 2. Start FF. 3. Actual Results: About 50% of the time the proxy-auth login panel comes up before the first browser window and the menu bar winds up not being initialized. If you give the correct credentials to the proxy-auth panel the startup page appears. If you then use the Firefox menu, the only one populated, to bring up the About panel the menu bar will be populated.

I'm putting this into OS Integration since it seems to be a race condition in the OS specific startup code. I'm attaching screen shots showing the menu bar.

Regarding comment #3, the picture is after entering the correct proxy-auth details and dismissing it. It shows the correct page having been fetched and rendered but the menu bar left as incomplete.

From the screenshot (the tell-tale 1-2px wide transparent window the sheet's attached to), this smells like a dupe of bug 424266.