Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50739 - Disable form and javascript support
Attached to Project:
Community Packages
Opened by sher (shedto) - Sunday, 11 September 2016, 17:03 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 11 September 2016, 18:26 GMT
Opened by sher (shedto) - Sunday, 11 September 2016, 17:03 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 11 September 2016, 18:26 GMT
|
DetailsDescription:
Using pdf forms with the current version of mupdf crashes the application. Simply clicking on a form input in a pdf file will cause the application to be unresponsive. When started from the console there will be a broken prompt for the input message. Since the form functionality is clearly completely broken and also requires javascript support, it would be best to disable form and javascript support at compiletime both for stability, usability and security reasons. Please note that Debian already does this. When using mupdf 1.9a+ds1-1.2 on debian testing the forms are ignored an javascript is completely disabled. https://packages.debian.org/stretch/mupdf Version: 1.9_a-5 Steps to reproduce: Open a pdf file with forms from commandline and click on a textinput box. Testfile attached |
This task depends upon
interactiveform_enabled.pdf