ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This last Firefox update had totally screwed up everyone's browser. Especially maps.

  • 3 ردود
  • 0 have this problem
  • 1 view
  • آخر ردّ كتبه cor-el

more options

This last Firefox update had totally screwed up everyone's browser. Especially maps. Half of my maps, especially on Find A Grave no longer work. I dont know what you guys did, but you need to fix it fast!

This last Firefox update had totally screwed up everyone's browser. Especially maps. Half of my maps, especially on Find A Grave no longer work. I dont know what you guys did, but you need to fix it fast!
Attached screenshots

الحل المُختار

OK< discovered the problem. I was still running Firefox in its Safe Mode, because that's the only way I could get it to work this morning, especially for all the maps I use. Once I discovered this, I logged out and when it came back up, all my maps were OK. I dont know what kind of tweaks people are doing, but for Gods sake stop! Firefox has worked perfectly for me for 25 years, even before it was Firefox.

Read this answer in context 👍 0

All Replies (3)

more options

If you have the AdBlocker Ultimate extension extension then this is likely a problem with this extension as there have been several reports.

  • 1847380 - Adblocker Ultimate preventing pages from displaying correctly

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

more options

الحل المُختار

OK< discovered the problem. I was still running Firefox in its Safe Mode, because that's the only way I could get it to work this morning, especially for all the maps I use. Once I discovered this, I logged out and when it came back up, all my maps were OK. I dont know what kind of tweaks people are doing, but for Gods sake stop! Firefox has worked perfectly for me for 25 years, even before it was Firefox.

more options

That is likely because WebGL is disabled in Troubleshoot Mode. The Web Console would have shown an error message or warning.