https://bugs.kde.org/show_bug.cgi?id=436870
John Scott <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from John Scott <[email protected]> --- Discussion on this bug report seems to have strayed from the subject. For example, it is irrelevant that OpenAction is sometimes used as an anti-feature, such as to entice users to download Adobe's proprietary software. Also, the submitter's example of opening a URL to Adobe's homepage as an OpenAction, even if a distasteful example, should not be used to discredit this issue report—in fact, it's evidence of its legitimacy. The fact is that the OpenAction entry in document catalogs is specified by the pertinent international standards. Today I've run into this issue in creating a document that's *supposed to* use JavaScript to display a warning when a document is opened. Okular already works with JavaScript in documents for the most essential purposes, but (on my Debian Trixie machine, using Okular 25.04.2 with Poppler 25.03.0), it does appear Okular ignores the OpenAction directive. In a moment I will upload a minimal PDF, along with the LaTeX code used to generate it, so the issue can be looked into. From doing a search on Poppler's source tree, the only place I see OpenAction seriously mentioned is in Catalog.cc, to implement a function `std::unique_ptr<LinkAction> Catalog::getOpenAction() const;`. It appears Poppler expects user agents like Okular to use this function when a document is "opened" (however the user agent defines that notion), since it doesn't take care of this on its own. That seems like it'd be pretty easy, right? -- You are receiving this mail because: You are watching all bug changes.
