288677 - Toolbar won't allow customization

Status: RESOLVED INCOMPLETE

(Firefox :: Toolbars and Customization, defect)

Description

[Bryan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Firefox 1.0.2

Toolbar will not let me remove the go button in version 1.0.2 or buttons that
I've dragged onto the toobar.

Reproducible: Always

Steps to Reproduce:
1.RIght click and select cusomize on the toolbar menu
2.Click restore default set
3.Try and remove the go button

Actual Results:  
It wouldn't let me remove the go button

Expected Results:  
Put the go button back into its set of unused icons

I've switched back to version 1.0 and the toolbar customization works fine; only
in 1.0.2 am I having problems.

Comment 1

[Bob Gabert]

I added a separator and 'Print this page' icon to the Navigation Toolbar. They
cannot be moved back to the Cusomize Toolbar dialog. The Restore Default Set
button removes them, but they return when Firefox is restarted.

Comment 2

[d.longfield]

After making changes to toolbar, customization reverts back to default list
after system  is idle or when browsing through multiple web pages.
You may think that the severity of this is minor, but it's damned annoying none
the less!
[e-mail]

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.