Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

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

  • 1 odgovor
  • 12 ima ovaj problem
  • 5 prikaza
  • Posljednji odgovor od 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.

Izmjenjeno od the-edmeister

Svi odgovori (1)

N73VDK
N73VDK Vlasnik pitanja
more options

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


-- Solved --