Support

Problem:
Links to PDF files were not opening properly in Safari. The width was 100% but the height was only at about 10%.

The console revealed the following error:

[Error] Refused to apply a stylesheet because its hash, its nonce, or 'unsafe-inline' appears in neither the style-src directive nor the default-src directive of the Content Security Policy.

Solution (sorta):

We determined that the Admin Tools htaccess maker setting labeled "Disable client-side risky behavior in frontend static content" resulted in the blockage of Safari's PDF viewer styling due to the styling being inline.

This ticket is meant mostly to be informative, in the event others experience the same issue. However, you may want to consider eliminating pdf/PDF from the file formats that have the "risky behavior on frontend" CSP applied when that setting is enabled.

Hi Nicholas - 

Yes, we understand, and thank you for the reply. However, what I hoped to save someone else time in troubleshooting by posting this ticket is that unique to the Safari browser, apparently, the browser's built-in PDF viewer inserts inline styling to simply display a PDF file. We are not loading any external resources in our own doing and we simply have links to local PDF files. These work as expected in all other tested browsers, but in Safari local PDFs will not display as expected unless style-src in the CSP includes 'unsafe-inline' due to Safari's less-than-stellar PDF viewing and unfortunate standing as the iPhone's default browser. 

So, with the Admin Tools default file formats listed in “Frontend file types allowed in selected directories” in the folders defined in “Frontend directories where file type exceptions are allowed”, and having "Disable client-side risky behavior in frontend static content" enabled, this will result in simple local PDF files unable to load properly in Safari when stored in a defined frontend directory.