Google Maps

[wis3f1sh]

BEFORE YOU BEGIN

I have attempted the following troubleshooting suggestions:

• [ ] The issue persists when using Firefox in Troubleshoot Mode.
• [ ] Disabled DNS-level content blocking (AdGuard Home, NextDNS, Control D, RethinkDNS, PiHole, etc), cleared my DNS cache, and used my ISP's DNS resolver (if applicable).
• [ ] Cleared website data, restarted Firefox, and my issue persists.
• [ ] I have created a new profile. The issue persists when using the current user.js file on GitHub. (Must be in a new profile and a new user.js!)

REPORT

Describe the bug on google maps site "globe mode" is not available and zooming is intermittent

To Reproduce I go to google maps and observe the inability to turn on "globe mode" and intermittent zooming

1. Go to google maps
2. Click on layers
3. Scaling the map
4. See error

Expected behavior globe mode on google maps and smooth zooming

Screenshots If applicable, add screenshots to help explain your problem.

https://github.com/yokoffing/Betterfox/assets/97912016/18031d5b-e705-4ab8-b8d5-991287f3071d

Desktop (please complete the following information):

• Windows 10 22H2 x64
• Firefox
• 116.0

Additional context Add any other context about the problem here.

[yokoffing]

Summary: I cannot reproduce on Firefox Stable using a new profile or when using the current user.js. However, I can reproduce on my build with Firefox Nightly.

There are many bug reports across various browsers reporting this issue in the past 5 years, but none of them I've found post what the solution was. Many seem to point to the browser not being able to use WebGL. You can test if Firefox can use WebGL with this site: https://get.webgl.org/

On Stable (with or without user.js) and Nightly (without the user.js):

On Nightly (with my customized user.js):

Update: After updating my NVIDIA graphics driver, testing the new profiles, and switching back to my default profiles, https://get.webgl.org/ loaded correctly in Nightly, and I was able to use Globe mode on Maps.

[wis3f1sh]

Indeed, the essence of the problem is in the enabled parameter about:config webgl.disabled. After disabling it, the problem is solved. The only remaining question is whether this parameter is in user.js or related to something else?

[yokoffing]

webgl.disabled is not in the user.js. It's stated in the README that we don't break user experiences like this.

Most issues are due to users toggling prefs outside the user.js, which is why the BEFORE YOU BEGIN section exists for bug reports...

In the future, bug reports not following through with self-troubleshooting will be auto-closed.