Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Firefox 4 Menu Bar - When I hover over or select a menu bar item, the menu bar sub-menu becomes transparent and unreadable. Is this a known issue that can be corrected with an update or is it functionality that is not designed to work with this version?

  • 2 odgovora
  • 19 ima to težavo
  • 6 ogledov
  • Zadnji odgovor od lancelot2525

lusciousdan
lusciousdan
more options

Firefox 4 Menu Bar - When I hover over or select a menu bar item, the menu bar sub-menu becomes transparent and unreadable. Is this a known issue that can be corrected with an update or is it functionality that is not designed to work with this version?

Firefox 4 Menu Bar - When I hover over or select a menu bar item, the menu bar sub-menu becomes transparent and unreadable. Is this a known issue that can be corrected with an update or is it functionality that is not designed to work with this version?

Vsi odgovori (2)

jalinds
jalinds
more options

I stopped having this issue when I enabled the menu bar. Right-click on an empty section of the tab strip and put a check next to menu bar. It was even still working fine when I disabled the menu bar again later.

lancelot2525
lancelot2525
more options

If this happens on monitor 2 of 2, this problem has been solved here:

http://support.mozilla.com/en-US/questions/794823#answer-157988

Go to "Firefox"--> "Options" --> "Advanced" Then un-check "Use hardware acceleration when available"

While not verified, I believe this problem is due to an SLI configuration where the focus is on monitor 1. (I.e acceleration is available, but only on monitor 1.)