Bug 145653 - FORMATTING Regression in numbering List Style, Separator disappears when Number set to None
Summary: FORMATTING Regression in numbering List Style, Separator disappears when Numb...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-11-13 08:39 UTC by Emanuele Gissi
Modified: 2022-05-03 11:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Demo of the regression (287.54 KB, application/vnd.oasis.opendocument.text)
2021-11-13 08:41 UTC, Emanuele Gissi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emanuele Gissi 2021-11-13 08:39:56 UTC
Description:
When applying a List style in the text the requested separator is *not displayed* in the text, but it is still correctly shown in the List Style <Preview>, if the <Number> is set to "None".

See example file.

Steps to Reproduce:
First, open a new text document.
Then:

1. create a new numbering List Style
2. open the <Customize> panel of the new List Style
3. add separator strings in the <Before> and <After> fields
4. set the <Number> field to "1,2,3..."
5: apply the new style to a list of items.

The numbering and the separator are correctly displayed both in the <Preview> and in the text. No bug here.

1. create a new numbering List Style
2. open the <Customize> panel of the new List Style
3. add separator strings in the <Before> and <After> fields
4. set the <Number> field to "None"
5: apply the new style to a list of items.

As requested, no numbering is shown. On the other hand, the requested separator is *not displayed* in the text, but it is still correctly shown in the List Style <Preview>.

See the attached example for a detailed explanation.


Actual Results:
The requested separator is *not displayed* in the text, but it is still correctly shown in the List Style <Preview>.

Expected Results:
The requested separator should be *displayed* in the text, as it is shown in the List Style <Preview>. This works ok in Libreoffice 7.1.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.2.2.2
Build ID: 20(Build:2)
CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: it-IT (it_IT.UTF-8); UI: en-US
Calc: threaded
Comment 1 Emanuele Gissi 2021-11-13 08:41:21 UTC
Created attachment 176226 [details]
Demo of the regression
Comment 2 Emanuele Gissi 2021-11-13 08:47:41 UTC
Maybe linked to:
https://bugs.documentfoundation.org/show_bug.cgi?id=145610
Comment 3 Emanuele Gissi 2021-11-13 08:56:32 UTC
Added vasily.melenchuk@cib.de, because I saw he was working on related issues.
Sorry, if I am mistaken. Thank you for your help, in any case.
Comment 4 Vasily Melenchuk (CIB) 2021-11-13 09:05:25 UTC
Hi Emanuele,

Can you check with daily builds (https://dev-builds.libreoffice.org/daily/)?
Seems this problem already fixed recently or at least I was not able to reproduce it with recent master:

Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 8e8e72f08b01a284cf1a90b888d48acfb6a33d2e
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-US (C); UI: en-US
Calc: CL
Comment 5 Emanuele Gissi 2021-11-13 09:09:21 UTC
Sure, will do immediately
Comment 6 Emanuele Gissi 2021-11-13 09:42:03 UTC
I confirm it is fixed with:

Version: 7.3.0.0.alpha1 / LibreOffice Community
Build ID: a3c29ae3d906f4692090bd4e5dab29623c66014a
CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: it-IT (it_IT.UTF-8); UI: en-US
Calc: threaded

Thank you very much, I owe you a pizza (a real tasty Italian one ;-)
Comment 7 Emanuele Gissi 2021-11-13 09:42:41 UTC
Fixed in:

Version: 7.3.0.0.alpha1 / LibreOffice Community
Build ID: a3c29ae3d906f4692090bd4e5dab29623c66014a
CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: it-IT (it_IT.UTF-8); UI: en-US
Calc: threaded
Comment 8 Xisco Faulí 2022-05-03 11:11:01 UTC
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.