If you updated to Firefox 160 over the past couple of days and suddenly found yourself staring at a completely blank white screen in Google Docs, your computer isn’t dying. A weird rendering bug in the latest browser update is messing up Google Workspace apps for a handful of Mac users.

We have spotted reports about this bug popping up on Reddit and Mozilla’s own support forums. According to user reports, Google Docs pages are loading with invisible text while Google Sheets are turning into a patchy mess of black and white blocks.

firefox-160-google-sheets-docs-bug-complaint

“Google Docs are completely white-ed out…except for images. I can type, and clearly the text I type is there,” one frustrated iMac user wrote on Mozilla’s forum, adding that their work has basically “ground to a halt.”

Here are the screenshots they shared for reference:

firefox-160-white-blank-sheet-bug-1

firefox-160-black-blank-bug

Your data is still safe underneath the visual glitch, and you can actually see the text in a spreadsheet cell if you click directly inside it, though it vanishes again the second you hit enter.

I tried replicating the bug on my M2 MacBook Air after grabbing the update, and both Docs and Sheets loaded up without a hitch. Digging through the complaints, the issue seems to be hitting older Intel-based Macs the hardest.

With version 160, Mozilla switched how Firefox handles graphics on macOS over to Apple’s Metal API. That change was supposed to make websites run smoother, which is a nice perk alongside new additions like Mini Window multitasking and better Picture-in-Picture controls, yet older Mac hardware clearly isn’t playing nice with it.

Thankfully, you don’t have to abandon Firefox for Chrome or Safari while waiting on an official patch.

Reddit user obsidianspider shared a quick fix that gets things back to normal. You just type about:config into your Firefox address bar, hit enter, and search for webgl.disable-angle. Flip that setting to TRUE and restart the browser.

If messing with hidden config menus isn’t your thing, another user pointed out that you can just head into your normal Firefox Settings, uncheck “Use recommended performance settings,” and turn off hardware acceleration.

 
✦
PiunikaWeb’s Take

Graphics backend changes are notoriously tricky to pull off without breaking something on legacy hardware. Switching to Apple’s Metal API makes complete sense for modern Apple Silicon machines, though older Intel Macs and setups running OpenCore Legacy Patcher often get caught in the crossfire during these transitions.

Since Mozilla is already pushing forward with the Firefox v161 beta that brings back classic themes and custom URL shortcuts, we expect the team to either push a minor hotfix for version 160 or quietly blacklist the problematic Intel GPU drivers from the new Metal renderer pretty soon. Until that happens, flipping the WebGL flag is a painless fix that beats switching browsers.

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Dwayne Cubbins
3201 Posts

I cover fast-moving stories across apps, online platforms, and everyday tech — phones, wearables, consoles, and whatever else people are fighting with this week. Bugs, rollouts, scams, policy enforcement, and the occasional internet-culture rabbit hole are all fair game. My goal is simple — make confusing tech news readable. When I'm not working, I'm working out or chilling with my dog. Got a tip? You can find me on X @dcubbins.