Bizarre problem with Google satellite / globe view / 3D
Since upgrading to v92.0, when satellite and globe view are turned on at Google Maps, a line extending from top left to bottom right corner bisects two different views within the view: the one to the bottom left of the line is normal, the one to the top right of the line is rotated 90° counterclockwise. Cursoring through the view moves both views, as you might imagine. I tried to motion-screen-capture the cursor-through, but the capture app wouldn't capture anything. The problem does not occur with other browsers.
All Replies (4)
You can check the Web Console for WebGL related messages.
You can try to disable hardware acceleration in Firefox.
- Settings -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available" - https://support.mozilla.org/en-US/kb/performance-settings
Close and restart Firefox after modifying the setting to make changes effective.
You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.
I have a SLEW of WebGL issues, note that "RENDERER" one early. Take a look:
Some cookies are misusing the recommended “SameSite“ attribute 18 WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. rs=ACT90oE1z5kqgCi2TxmVDgG1YRY-_jcd9A:2180:256 WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. 4M_hU0z2aGWsE6Fh5g73T3aOvXi4a4lK__VWYOQ1wYI.js line 1 > eval line 5418 > eval line 1 > eval:1:67 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive. Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified Some cookies are misusing the recommended “SameSite“ attribute 2 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 2 moz-extension:50:25 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Alpha-premult and y-flip are deprecated for non-DOM-Element uploads.
Soooo, does this mean GMaps is dissing Firefox? I think so!
Unchecked the boxes you suggested, did not address the problem.
If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, DuckDuckGo PE, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.
- make sure your extensions and filters are updated to the latest version
- https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content. You can click shield icon for more detail and possibly disable the protection. You can check the Web Console for related messages about blocked content.
- https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
- https://support.mozilla.org/en-US/kb/smartblock-enhanced-tracking-protection
- https://support.mozilla.org/en-US/kb/trackers-and-scripts-firefox-blocks-enhanced-track
You can try these steps in case of issues with webpages:
You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).
"Remove the Cookies" for websites that cause problems:
- Settings -> Privacy & Security
Cookies and Site Data: "Manage Data"
"Clear the Cache":
- Settings -> Privacy & Security
Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear
Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window