This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

[Solved] Customize in Firefox 7.0a2 greys out, and won't allow clicking on bookmarks toolbar.

  • 1 reply
  • 12 have this problem
  • 10 views
  • Last reply by N73VDK

N73VDK
N73VDK
more options

Since the latest update in Aurora from 6.0a2 to 7.0a2, the 'customize' context menu option on the toolbars will grey out when clicked, without actually popping up the customize panel, and the bookmarks toolbar becomes unusable. The bookmarks toolbar problem can be fixed by closing and reopening Aurora, however this bug seems to be persistent each time 'customize' is clicked.

I have not been able to find anywhere to notify bugs for the Aurora update channel so decided this was the best place to ask, searching for this on Google came out with no results, so assuming it may just be a problem on this install.

Since the latest update in Aurora from 6.0a2 to 7.0a2, the 'customize' context menu option on the toolbars will grey out when clicked, without actually popping up the customize panel, and the bookmarks toolbar becomes unusable. The bookmarks toolbar problem can be fixed by closing and reopening Aurora, however this bug seems to be persistent each time 'customize' is clicked. I have not been able to find anywhere to notify bugs for the Aurora update channel so decided this was the best place to ask, searching for this on Google came out with no results, so assuming it may just be a problem on this install.

Modified by the-edmeister

All Replies (1)

N73VDK
N73VDK Question owner
more options

UPDATE: I have found out that this is caused by an add-on and have notified the developer.


-- Solved --