![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Google Sheets "Unable to Load File" in Firefox
I am attempting to open files in Google Sheets and receive an "Unable to load file" error every time. The problem persists only in Firefox - files open normally in Chrome and Safari (I am on macOS Sierra 10.12.3). It also only applies specifically to Google Sheets - all other files in Google Drive (Docs, Forms, Slides, etc.) load normally.
I have tried: - completely clearing cache and cookies - disabling all extensions - updating Firefox from 50.1 to the latest 51.0
None of these have worked. Any other solutions I can try??
გადაწყვეტა შერჩეულია
Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?
You can check the Web Console (Firefox/Tools > Web Developer) for error messages about blocked and unsafe content. You can check the Network Monitor to see if content is blocked or otherwise fails to load.
You can use "Ctrl+F5" or "Ctrl+Shift+R" to reload the page and bypass the cache to generate a fresh log.
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- Switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Appearance
- Do NOT click the "Refresh Firefox" button on the Safe Mode start window
- https://support.mozilla.org/kb/Safe+Mode
- https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").
Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks and history and cookies and passwords and cache and exceptions, so be cautious. If you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.
Can't recover from this 'forget' unless you have a backup of involved files.
If you revisit a 'forgotten' website then data from that website will be saved once again.
პასუხის ნახვა სრულად 👍 1ყველა პასუხი (2)
შერჩეული გადაწყვეტა
Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?
You can check the Web Console (Firefox/Tools > Web Developer) for error messages about blocked and unsafe content. You can check the Network Monitor to see if content is blocked or otherwise fails to load.
You can use "Ctrl+F5" or "Ctrl+Shift+R" to reload the page and bypass the cache to generate a fresh log.
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- Switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Appearance
- Do NOT click the "Refresh Firefox" button on the Safe Mode start window
- https://support.mozilla.org/kb/Safe+Mode
- https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
You can remove all data stored in Firefox from a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").
Using "Forget About This Site" will remove all data stored in Firefox from that domain like bookmarks and history and cookies and passwords and cache and exceptions, so be cautious. If you have a password or other data from that domain that you do not want to lose then make sure to backup this data or make a note.
Can't recover from this 'forget' unless you have a backup of involved files.
If you revisit a 'forgotten' website then data from that website will be saved once again.
Thank you for the "Safe Mode" recommendation and links - the problem did not persist when loading in Safe Mode. I traced the issue back to the Privacy Badger extension, which just pushed an update earlier today, so I suspect that had something to do with it. Temporarily disabled the extension and reported the issue.
Thanks again!