User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021014 Phoenix/0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021014 Phoenix/0.3 When right-mouse clicking the navigation toolbar and choosing the "customize" option, customizing works. However, when done adding a button (such as "new tab"), the file menu is inaccessible. Reproducible: Always Steps to Reproduce: 1. right mouse click near the stop button 2. choose customize 3. add a button 4. click done Actual Results: the file menu is inaccessible Expected Results: returned file menu to being accessible
Worksforme with today's builds on linux and win2K. Did you install to a clean directory and remove your old profile as recommended in the release notes?
*** Bug 174774 has been marked as a duplicate of this bug. ***
I saw this problem too. After moving the whole profile directory the problem disappears. (Of course I then had to copy over the old bookmarks file, cookies file, prefs file, and re-customize the toolbars... blah.)
*** Bug 175261 has been marked as a duplicate of this bug. ***
Yes, following the instructions in the release notes fixes this. Not a bug.
Mass-verifying of old bugs.
Taking QA Contact
I'm seeing this bug on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040510 Firefox/0.8.0+ with a clean profile. Today's Win32 build works fine. Steps to Repro: 1a. View | Toolbars | Customize -or- 1b. Right-click on a toolbar, Customize. 2. Do something (or nothing). 3. Press Done. Expected Results: Menus should work okay. Actual Results: Menus are disabled until browser is restarted. I have a feeling this *may* have the same root cause as bug 243210, but I'm not sure on that.
Reassign to default owner/QA, and set to NEW.
(In reply to comment #8) Same problem here. checkout finish: Mon May 10 22:28:26 EDT 2004 ... Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040510 Firefox/0.8.0+
Going to close this and file a new bug instead, since the cause is different.
(In reply to comment #11) > Going to close this and file a new bug instead, since the cause is different. I've filed bug 243262 to address the new regression.