Bug 156024 - Rich Text Content Control Remains interactive after converting from DOCX to PDF
Summary: Rich Text Content Control Remains interactive after converting from DOCX to PDF
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
7.5.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: DOCX-Content_Control
  Show dependency treegraph
 
Reported: 2023-06-22 18:22 UTC by Nolan
Modified: 2023-09-06 22:32 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file as ODT (9.60 KB, application/vnd.oasis.opendocument.text)
2023-09-04 15:55 UTC, Buovjaga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nolan 2023-06-22 18:22:24 UTC
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
Comment 1 Buovjaga 2023-09-04 15:54:52 UTC
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
Comment 2 Buovjaga 2023-09-04 15:55:12 UTC
Created attachment 189342 [details]
Example file as ODT