Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Learn More

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Blank context menu with Hardware Acceleration

  • 2 risposte
  • 2 hanno questo problema
  • 8 visualizzazioni
  • Ultima risposta di FredMcD

more options

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything.

This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing.

Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs.

I need to know how to resolve this without sacrificing Hardware Acceleration.

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything. This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing. Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs. I need to know how to resolve this without sacrificing Hardware Acceleration.

Soluzione scelta

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (2)

more options

Soluzione scelta

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

more options

That was very good work. Well Done.