Created attachment 161762 [details]
Writer file showing problem with Paragraph Style
Version: 22.214.171.124 (x64)
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win;
Locale: en-GB (en_GB); UI-Language: en-GB
1. Open the attached file. Note that the poetry, in addition to having a set "Paragraph Style", has also been customised by setting the indent in the horizontal ruler (can also be done from "Format > Paragraph" etc.).
(NOTE: According to the UK Style Bible—"New Hart's Rules" (OUP, 2005, p. 160)—poetry should be centred on the longest line on each page. This means that the indentation has be set manually for each page, and cannot be based purely on the global Paragraph Style indentation.)
2. Open the Poetry "Paragraph Style > Indents and Spacing" and set the "Line Spacing" to "Double" (say). Then press OK to quit dialogue.
EXPECTED RESULT: The Line Spacing should immediately change in the Paragraphs.
ACTUAL RESULT: Nothing happens. You have to press Ctrl + M (Clear Direct Formatting) for the changes to take effect. But this means that ALL the previously applied custom changes to indentation will be UNDONE as well, and have to be be reset page by page. PAINFUL.
I can understand why you MIGHT want custom paragraph properties (set from "Format > Paragraph") to be retained in the face of any changes made to the global Paragraph Style, but this control should be specific. E.g. In the above example, the line indentation for poetry was customised (using "Format > Paragraph"). But this should NOT stop changes to Paragraph Style "Line Spacing" being applied because the latter is a non-related property. And so on.
I confirm it with
Version: 126.96.36.199.beta1 (x64)
Build ID: 94f789cbb33335b4a511c319542c7bdc31ff3b3c
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
1. Open document
2. Double click of paragraph style "Poetry" => left alignment of text
3. Change line spacing of paragraph style to double => That works
Dear R. Green,
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!
Version: 188.8.131.52 / LibreOffice Community
Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
I can confirm that the self-same bug is present in the latest release. Follow the instructions in the opening post and the results are the same.