Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Learn More

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

  • 1 ответ
  • 12 имеют эту проблему
  • 10 просмотров
  • Последний ответ от 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.

Изменено the-edmeister

Все ответы (1)

more options

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


-- Solved --