After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785533 - Evince does not execute JavaScript of PDF forms
Evince does not execute JavaScript of PDF forms
Status: RESOLVED DUPLICATE of bug 338721
Product: evince
Classification: Core
Component: PDF
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-07-28 15:40 UTC by Uwe Stöhr
Modified: 2017-10-02 14:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Uwe Stöhr 2017-07-28 15:40:13 UTC 
Attachment #356517 [details] is a PDF form I created with the latest pdflatex. It fulfils the PDF form specification as is used as reference PDF form for the program LyX. The PDF looks and works fine using Adobe Reader under Windows. Under Linux using Evince 3.24.1 there are several bugs. (Attachment #356518 [details] is the TeX source code of the form.)

This report is about executing JavaScript:
- open the PDF and go to sec. 2.4 and there to the 2nd push button
- click the button.

result: nothing happens. The underlying JavaScript code is either not executed or Evince has overseen that the document contains JavaScript. Adobe Reader executes it correctly and shows the defined message about a fridge.
Since I cannot find a setting in the Evince preferences to block JavaScript I guess it is a bug.

If it is not a bug but a missing feature Evince should warn the user that he cannot completely use the form. (Many PDF forms from e.g. federal administration use JavaScript for hits and explanations about the different form fields.)
Comment 1 Germán Poo-Caamaño 2017-10-02 14:34:33 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 338721 ***