Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Google Calendar will not print, even in Private Window.

  • 3 respostas
  • 1 tem este problema
  • 1 exibição
  • Última resposta de Rehlyt

more options

We can not get Google Calendar to print when we click the gear icon at the top and select print. The first dialogue box will pop up, but when we click print it does nothing. The log shows multiple lines of this:

Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

How can we fix this? I have found no solution anywhere.

We can not get Google Calendar to print when we click the gear icon at the top and select print. The first dialogue box will pop up, but when we click print it does nothing. The log shows multiple lines of this: Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified How can we fix this? I have found no solution anywhere.

Todas as respostas (3)

more options

Here is a screenshot.

more options

What if you tried Chrome?

more options

Yeah, it works fine in other browsers. That isn't the point. My back office prefers to use the Firefox browser, and I just find it surprising that Mozilla does not have a fix for this.