Description: When exporting a Writer document with Form Controls as a PDF, it appears that the the export process is ignoring the value set in `Control Properties -> Vert. Alignment`. The setting is obeyed within Writer itself (when I turn off Design Mode), but in the PDF text entered in the fields is always centered vertically, even when `Vert. Alignment` was set to top, bottom or default. So far, I can confirm this is the case when PDF is viewed with Okular and Google Chrome Browser. Steps to Reproduce: 1. From the `Form Design` toolbar, click on the `Design Mode` button to enable design mode. 2. In the `Form Controls` toolbar, select `Text Box`. 3. Click and drag anywhere in the Document to create the text box. 4. Right click on the text box and select `Control Properties`. 5. In the Properties dialog, scroll down to where the `Vert. Alignment` option is, and try setting it to any value other than Middle or default. 6. Click on the `Export directly as PDF` button in the main toolbar. 7. Open the PDF with your favourite PDF viewer/editor (e.g. Okular, Google Chrome); it may ask if it should show forms, confirm with yes. 8. Enter some text in the text box. 9. Then go into Print Preview Actual Results: In print preview, the text appears vertically aligned in the middle of the text box, even though the value of `Vert. Alignment` was not set to middle. Expected Results: In print preview, the text should show up at the very top of the Text Box if `Vert. Alignment` was set to top, or at the very bottom of the text box if it was set to bottom. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: en-CA (en_CA.UTF-8); UI: en-US Debian package version: 1:7.0.4-3 Calc: threaded
I can confirm that the bug is present in Version: 7.0.4.2 (x64) Build ID: dcf040e67528d9187c66b2379df5ea4407429775 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-US Calc: threaded
Created attachment 189838 [details] Example file from Writer made per instructions
Created attachment 189839 [details] PDF export of the example file
Created attachment 189840 [details] Screenshot of the example file and its export in Evince
Dear stiliyan, 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