We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Google Calendar will not print, even in Private Window.

  • 3 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan Rehlyt

Rehlyt
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.

Alle antwurden (3)

Rehlyt
Rehlyt Fraacheigener
more options

Here is a screenshot.

WestEnd
WestEnd
more options

What if you tried Chrome?

Rehlyt
Rehlyt Fraacheigener
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.