Javascript action to open hyperlinks inside embedded pdf in a new window not working
Reported by
ggerard...@gmail.com,
Jul 19
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Steps to reproduce the problem: 1. Created a nice pdf in adobe acrobat pro 2. Created links in the document with the Javascript action provided there : https://answers.acrobatusers.com/How-I-open-hyperlinks-inside-embedded-pdf-window-q2104.aspx 3. Saved and opened in chrome 67 What is the expected behavior? While reading the pdf file in there browser (the goal is to open it from a website), I wish users can clic on links wich would open in a new tab. What went wrong? 1- button links won't work on chrome. Only text links begining with http:// in the visible text (not in action code) are recognized by Chrome 2- Those links in visible text won't open in a new tab. WebStore page: Did this work before? N/A Chrome version: Version 67.0.3396.99 (Build officiel) (64 bits) Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 30.0 r0 Hello, I don't remember if this feature was effective before but I think the Chrome PDF viewer is quite new so it would be good to improve it taking account of Adobe functionnalitys. For info, Firefox opens perfectly all the links in new tabs while MS Edge opens all the links but in the same tab (not working neither :| ). Thank you for your interest, Best regards Gaƫl
,
Jul 19
,
Jul 19
Can you provide an example PDF demonstrating this issue?
,
Jul 19
,
Jul 20
Hello, I uploaded a PDF file for test on my website : https://dev.gaelgerard.com/testpdf.pdf Thanks for the support
,
Jul 20
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 20
Looking through the PDFium code, we do have an implementation of app.launchURL in our code base. It is no-op though, with an explicit comment that this operation is considered unsafe and thus not supported. This appears to be a case where we have actively chosen to be non-compliant with the Adobe implementation. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted