Content Security Policies seem to harden after a a third party calls the print dialog
After a third party framework calls the print API the CSPs suddenly block unsafe-eval. Reloading the page allows the use of 'unsafe-eval' again.
Does access of the print API somehow harden the CSPs?
After a third party framework calls the print API the CSPs suddenly block unsafe-eval. Reloading the page allows the use of 'unsafe-eval' again.
Does access of the print API somehow harden the CSPs?