Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

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

  • 1 Mbohovái
  • 12 oguereko ko apañuãi
  • 10 Hecha
  • Mbohovái ipaháva 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.

Moambuepyre the-edmeister rupive

Opaite Mbohovái (1)

N73VDK
N73VDK Porandu apoha
more options

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


-- Solved --