Description: Radio buttons on a Writer document form exported to PDF are not selectable if the PDF is opened in Document Viewer. When the PDF is opened in a browser (tested in Opera) or on Windows using Acrobat Reader the radio buttons work as expected. Steps to Reproduce: 1. Create a new Writer document 2. Add a radio button form control 3. File / Export as / Export as PDF... 4. Ensure that Create PDF Form is checked and use format FDF 5. Export and save the PDF 6. Open the PDF in Document Viewer 7. Try to select the Radio button Actual Results: Radio button can't be selected. Expected Results: Radio button is selected. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Tried this on LO 6.3 (using Linux Mint Software repo) and LO 7.3 downloaded manually on Linux Mint 20.3 and Linux Mint 20.2 (two different systems)
Created attachment 179676 [details] Writer Document containing radio button control
Created attachment 179677 [details] PDF Document containing radio button control
I confirm the description but: - option button not working in xreader and xpdf but is working in Master PDF Editor and Adobe Reader 9 in Linux - not working in older PDF-Xchange Viewer is working in newer Xchange Editor and in Adobe Reader 2022 in Windows Still, it worked before LO 6.3 so I'll confirm, unless explained why this wouldn't be a bug. commit 76b5dca9dc0ff60f8f62cbecdee68f8f3b287ceb author Thorsten Behrens <Thorsten.Behrens@CIB.de> tdf#113448 don't export any font for radio buttons
Julien,m you fixed bug 127217 after a long time and many duplicates, can you please comment here.
(In reply to Timur from comment #4) > Julien,m you fixed bug 127217 after a long time and many duplicates, can you > please comment here. I gave a try on Windows, it works with Edge. I gave a try on Linux, Gnome viewer, it failed. Weird.
Miklos: How to know if the pdf is indeed correct? I tried to find some PDF online validator but not very useful. I mean, perhaps some PDF clients are buggy (since depending on the client, click may work or not).
https://docs.verapdf.org/cli/validation/ might be useful. I haven't tried it myself, I only recently discovered it. Last time I needed a PDF validator, I used https://www.pdf-online.com/osa/validate.aspx -- but that sucks a bit, as it's an online-only tool. I hope of these do what you need. :-)
(In reply to Miklos Vajna from comment #7) > https://docs.verapdf.org/cli/validation/ might be useful. I haven't tried it > myself, I only recently discovered it. It seems we need to retrieve the source, I suppose from https://github.com/veraPDF/veraPDF-validation then build, then test. I git cloned the repo, then noticed I had to install maven so Java tool. I haven't tried yet, I thought there would be standard tools (ideally in C/C++). > Last time I needed a PDF validator, I used > https://www.pdf-online.com/osa/validate.aspx -- but that sucks a bit, as > it's an online-only tool. I hope of these do what you need. :-) I had found this one but it just returned: " File testjul.pdf Compliance pdf1.6 Result Document does not conform to PDF/A. Details Validating file "testjul.pdf" for conformance level pdf1.6 The operator has an invalid number of operands. The document does not conform to the requested standard. The document doesn't conform to the PDF reference (missing required entries, wrong value types, etc.). The document does not conform to the PDF 1.6 standard. Done. " I wish it would be more verbose and indicate what are the pbs.
CC Thorsten in case they are aware of some pdf validator, better than verapdf.
Dear Lambert, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug