Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

Etsi tuesta

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.

Lue lisää

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

  • 1 vastaus
  • 12 henkilöllä on sama ongelma
  • 10 näyttöä
  • Viimeisin kirjoittaja 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.

Muokattu , muokkaaja the-edmeister

Kaikki vastaukset (1)

more options

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


-- Solved --