2
votes

This may not the the place to ask this question, but I've done a lot of searching and couldn't find any clear answer.

I have a PDF built with Adobe Acrobat DC with a lot of JavaScript (mostly changing some field value based on other fields, of just simple validation). That PDF is served from a Web Application. In MacOS, the PDF JavaScript does not seem to work when the PDF is opened in Safari or in the default MacOS preview application, but works perfectly fine when opened with Adobe Reader or chrome. However, starting Safari v11, adobe reader safari plugin has been discontinued/not supported, therefore the PDF first opens in the Safari default PDF viewer(with wrong values, because JS is not triggered I think) and only from there it can be opened in Adobe Reader, this is very bad UX.

I just wanted to make sure if PDF JavaScript is indeed not supported in Safari or am I doing something wrong?

2

2 Answers

1
votes

Hello this problem will get after new version is released.

The Acrobat/Reader plug-in for Apple Safari is based on Netscape Plug-In API (NPAPI), which is supported only till Safari version 11. In Safari 12, support for NPAPI plug-ins is removed, and hence the current Acrobat/Reader plug-in will not work.

see this helpx.adobe.com article

0
votes

This is usually caused by object-src in CSP.
If your pdf is self-hosted, you can set object-src: [ self ].