Description: For tables in a form, the font selection for the table is not applied to text columns if the column is defined as multi-line input. Instead, the default font is used. Steps to Reproduce: 1.Create a form with a table that has a text field. 2.Edit the properties for the table and select some font. 3.Verify that the selected font is applied to all columns including the text column. 4.Edit the properties for the text column and select Yes for multi-line input. 5.The font is no longer applied to the text column. Actual Results: The font selected for the table is not applied to the text column after selecting Yes for multi-line input. Instead, the column appears with the default font. Expected Results: The font selected for the table is applied to the text column after selecting Yes for multi-line input. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: OfficeDatabaseDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
Would it be possible you attach an example file?
Created attachment 175287 [details] Sample data base with form Demonstrates incorrect font for Col1 after selecting Yes for multiline input.
Thank you for your feedback. On pc Debian x86-64 with master sources updated today, I could reproduce this.
Created attachment 175297 [details] Example with table that allows modifications
Additional observations In the first example the form was read only -- ie input not allowed, modification not allowed. In the second example the form allows modifications. In this case clicking on any entry in the table changes the font from the table font to the default.
Thank you for the new feedback. Now the bug is confirmed but I don't know at all how to fix this so uncc myself. Hope someone will find a fix for this.
Dear Paul Ward, 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
Seems to be fixed.