The one caveat here is that browsers will, for security reasons, not allow linking to file:// URLs which should explain why this unfortunately cannot work for local files (which I'm assuming is what the problem is about). However, since relative links are unfortunately somewhat common, in the Firefox built-in version of PDF.js we'll attempt to create valid absolute links by using the current document URL in to improve the UX please refer to PR #7689. does show the correct pathnames in Trailer -> Root -> Pages -> Kids -> 0 -> Annots -> 0 -> A -> F and Trailer -> Root -> Pages -> Kids -> 1 -> Annots -> 0 -> A -> Fįirst of all, please note that using relative links in PDF files is never a good idea, since it means that the files aren't actually as portable as they ought be. I have also tried it in, it does not function as expected there either. Link to a viewer (if hosted on a site other than /pdf.js or as Firefox/Chrome extension): (On hover in Edge and Chrome, the mouse cursor is correctly changed to "pointer", if Firefox it is incorrectly the "text" cursor on click in Edge, the hyperlink text is surrounded by dotted lines, in Chrome and Firefox nothing appears to happen.)Īll other files (several hundreds of them) belonging to the same set of documents behave in the same way hyperlinks in the documents do not work when the documents are opened in a webbrowser, in a 'normal' pdf viewers they do.
The hyperlinked files are not opened / shown. In 'normal' pdf viewers (Acrobat DC, Foxit, PDF-XChange) it does function as expected. The first hyperlink should open file ""./././ra/400x.pdf"", the second one should open "./././ra/420x.pdf".īy the way, the attached file 1260415x.pdf is also in the same folder (/Datas/War/EPC/War_00/Typ126/Case1/ra/67/00 is the complete path). What is the expected behavior? (add screenshot)
0 kommentar(er)
