Created attachment 188158 [details] Set the attribute Hidden in character style Dummy to see the spacing issue I have a list with all the text in some paragraphs having a character style, Dummy, based on "No character style". If I apply Hidden attribute to the character style the paragraph disappears as expected but the line spacing is deeper where the text was hidden. The list remains uneven even if scrolled to another page and back. If I toggle Formatting Marks, click Print preview, or close a re-open the document the list becomes evenly spaced again. First investigated from Ask.LibreOffice answer but I feel I have seen the effect in other lists. https://ask.libreoffice.org/t/how-do-you-start-a-nested-list-on-the-same-line-as-the-parent-list-item/35529/14?u=earnestal Might apply to only Windows installations. Tested on: * LO 7.5.3.2 and LO 7.5.5.1 new parallel installation * A second Windows 11 computer (LO 7.3.6.2) with same result In the attached NestedListSameLine3.odt set the attribute Hidden in the character style "Dummy" to see the effect. I have included a screenshot taken from my computer. Version: 7.5.5.1 (X86_64) / LibreOffice Community Build ID: 2c5e46c1980ec5241359fd65d751dc518205e7af CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-NZ (en_NZ); UI: en-GB Calc: CL threaded
Version: 7.5.3.2 (X86_64) Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded I carefully double-checked because I initially had not the exact same procedure as EarnestAl, but not matter how I tweak the visibility flags, with or without formatting marks, sample rendering is exactly as expected under my Linux configuration. So, probably a divergence in the Windows-specific implementation part.
Repro. Already seen in oldest of Linux 43all repository. There you have to first turn formatting chars off. In old versions having formatting chars on also kept the hidden text visible. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 518fa99dd7693d64a53e404a065090aedc0002b1 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 14 August 2023 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Dear Alistair Saywell, 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
Appears to be solved in LibreOffice 24.8.3.2 and later Version: 25.2.5.2 (X86_64) / LibreOffice Community Build ID: 03d19516eb2e1dd5d4ccd751a0d6f35f35e08022 CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-GB Calc: CL threaded Cheers Alistair
Indeed, testing with attachment 188158 [details] I don't see the issue. Arch Linux 64-bit Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1313be884c4ded639a5f53694c82a1cf2e77fe70 CPU threads: 8; OS: Linux 6.15; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: CL threaded Built on 12 August 2025