Bug 93223

Summary:	Effects of applying styles "List 1" vs. "Numbering 1"
Product:	LibreOffice	Reporter:	Ulrich Windl <u20230201>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cno, u20230201
Priority:	medium
Version:	4.3.7.2 release
Hardware:	All
OS:	All
Whiteboard:
Crash report or crash signature:		Regression By:

Description Ulrich Windl 2015-08-07 06:26:05 UTC

I'm not sure wether this "works as designed", but it's "working against expectation":
When I have a lin of body text, and I apply the parapgraph style "List 1", the paragraph gets a bullet and some indentation. However if I apply the paragrapgh style "Numbering 1", I neither get a number, nor do I get indentation.
My expectaion was that the numbering style would add some numbering to the paragraph.

Comment 1 Ulrich Windl 2015-08-07 06:31:58 UTC

I found out this: "List 1" uses numbering style "List", while "Numbering 1" uses numbering style "none".

Comment 2 Cor Nouws 2015-08-08 13:50:22 UTC

Hi Ulrich,

Thanks for the report!
I do not see the problem in 5.0.0.5 and 4.4.5.2...
Can you please check a recent version.
Or add a test file, if it persists?

Cheers,
Cor

Comment 3 Xisco Faulí 2016-09-11 10:30:20 UTC Comment hidden (obsolete)

Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

Sun, 11 Sep 2016 12:29:16 +0200

Comment 4 Ulrich Windl 2016-09-12 06:58:00 UTC

It seems to be fixed in 5.1.4.2

Comment 5 Cor Nouws 2016-09-12 20:32:40 UTC

thanks for checking and replying Ulrich,

We set to WorksForMe if we don't know a commit that resolved this.