Søg i Support

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

Google Calendar will not load through Firefox. Works fine in Microsoft Edge

  • 3 svar
  • 2 har dette problem
  • 40 visninger
  • Seneste svar af cor-el

more options

Starting today, Google Calendar will not load. There is none of my data in it. I cannot navigate. This is only in Firefox. A blue color streams across the top of the screen as if it is trying to load.

Starting today, Google Calendar will not load. There is none of my data in it. I cannot navigate. This is only in Firefox. A blue color streams across the top of the screen as if it is trying to load.

Valgt løsning

I've recently seen quite a few reports of issues with accessing Google Calendar, so it looks that something is seriously wrong. You can check the Web Console for possible error messages.

You can try to hide and show this content to see if that has effect.

There has been a bug report created where you can follow the progress.

  • Bug 1688211 - Firefox sometimes failed to load Google Calendar

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

Læs dette svar i sammenhæng 👍 1

Alle svar (3)

more options

Valgt løsning

I've recently seen quite a few reports of issues with accessing Google Calendar, so it looks that something is seriously wrong. You can check the Web Console for possible error messages.

You can try to hide and show this content to see if that has effect.

There has been a bug report created where you can follow the progress.

  • Bug 1688211 - Firefox sometimes failed to load Google Calendar

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

more options

I solved it by shutting down and then removing all the cookies. I also made the cookie folder much smaller and moved it to a remote drive.

more options

Google appears to have fixed this issue by reverting the change that caused it as reported in the bug report I linked above.