Description: .docx files containing rich text content control fields remain as interactive fields when converting to .pdf using the core CLI version 7.5.n. Previous versions (We have previously used 7.0 to 7.4) did not appear to have this issue. Steps to Reproduce: 1. Create a .docx file that contains a Rich Text Content field 2. Run the following command: libreoffice --headless --nolockcheck --nodefault --nofirststartwizard --nologo --norestore --convert-to pdf:writer_pdf_Export:PDFUACompliance=True <File> 3. Open the resulting PDF Actual Results: Rich Text Content Fields remain as interactive - user is able to change the content of the fields from the PDF file view. Expected Results: The Rich Text Content Fields are no longer interactive, and contain the content from the .docx file. The user cannot change the content of the field from the PDF view Reproducible: Always User Profile Reset: No Additional Info: Command is run on headless Ubuntu 20.04.1 LTS 7.5.2.2 Libreoffice CLI
Content controls were not exported to PDF at all before 7.5: https://wiki.documentfoundation.org/ReleaseNotes/7.5#Writer This is not dependent on command line exporting or the Universal Accessibility option. What I noticed is that exporting from DOCX results in a field that is the width of one character. Exporting from ODT results in the same, BUT only the first letter of the content control text is visible. Steps in Writer: 1. Form - Content Controls - Rich Text 2. Form - Content Controls - Properties 3. Uncheck "Content is placeholder text", OK 4. If you change the text, first click to focus into the control field, so you don't lose it Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cc7d6211bc01e5ec84dbad542605d2e93dea925c CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 03c43d303b6d32dc4c39bd273d446b66a3e6c42d CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 4 September 2023
Created attachment 189342 [details] Example file as ODT
Dear Nolan, 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