Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox 37.0.2 upside down bug

  • 2 Antworten
  • 2 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von wyrenth

more options

I update firefox to 37.0.2

In change log is writen that google maps upside down bug is fixed but is still not.

With Nvidia latest drivers installed, google maps is still upside down on win 7 x64

On XP with integrated ati card all is OK in 37.0.1 and also now in 37.0.2, problem is still on Pc that have Nvidia card, here map is still upside down.

I update firefox to 37.0.2 In change log is writen that google maps upside down bug is fixed but is still not. With Nvidia latest drivers installed, google maps is still upside down on win 7 x64 On XP with integrated ati card all is OK in 37.0.1 and also now in 37.0.2, problem is still on Pc that have Nvidia card, here map is still upside down.

Alle Antworten (2)

more options

This actually did not get fixed in 37.0.2 (the bug fixed in 37.0.2 was another issue with google maps, not the upside down bug). Please disable Hardware Acceleration to use Google Maps until this is fixed. Turning off hardware acceleration

more options

This issue occurs for me when OMTC is disabled and Hardware Acceleration is enabled. To remedy this, go into about:config and set the following:

  • layers.offmainthreadcomposition.enabled = true

Unfortunately, disabling OMTC and enabling Hardware Acceleration is a fix for text rendering issues in Firefox. So you're forced to choose between readable text and readable maps.

Google Chrome does not appear to suffer from this issue. I'd really prefer not to migrate, but this "pick your poison" complication is starting to press the issue...