Bug 69813 - FORMATTING numbering lists styles and paragraph styles do not apply correctly
Summary: FORMATTING numbering lists styles and paragraph styles do not apply correctly
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.5.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-25 14:33 UTC by quantum.projects
Modified: 2017-12-09 15:49 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description quantum.projects 2013-09-25 14:33:12 UTC
Machine Specification:

Intel Core i5-460M, 2.53GHz. 4Gb RAM, Windos 7 Home Premium 64bits.

Problem:
Libreoffice v. 4.0.5.2, Writer, Numbering Lists and Paragraph Styles.

Pre-Bug Steps

1. I've created a numbering style named Standard Numbering List, and I've assigned different alignment and indentation options for each one of its levels.

2. Then, I assigned that numbering style to a paragraph style named Numbered Paragraph, which has no indentation defined. Space between paragraphs was the only customized option under Indents & Spacing. Its Outline is "Body Text".

Bug:

3. When I select and apply that Paragraph Style (Numbered Paragraph) for the line I'm currently on (F11 => double-click on the desired paragraph style), the indentation I've defined for the Numbering List is not used. The numbering is activated, but the numbers and text are placed next to the left margin regardless of the aligment and indentation options I've defined. This remains valid even if I demote levels, with or without subpoints (they all align exactly at the same point on the left margin).

4. However, if I manually select that line, and the previous or the next ones, and double-click on my custom numbering style, the indentation and aligment options are correctly applied to all levels. 

5. Selecting just the target line, and double-clicking on either the custom paragraph style or the custom numbered list style does not correct the indentation and the aligment.

6. Therefore, every time I want to apply a paragraph style to a line that is supposed to be numbered accordingly to a custom numbered list style, I have to manually select that line after I write it, along with other lines, and manually apply the Numbering List style.

7. Doing step 6 using the Paragraph Style instead of the Numbering Style won't correct the misalignment.

Expected Behavior:

1. With the blinking cursor on the target line, double-click on the Custom Paragraph Style to which a Numbering List Style was assigned.

2. Apply to that line the correct indentation and aligment options set for that Numbering List Style + Paragraph Style Combo.

3. Sublevels should use the corresponding alignment and indentation options assigned to them.
Comment 1 quantum.projects 2013-09-25 14:51:19 UTC
Workaround

1. If you create a fresh new Paragraph Style originally linked to <<-None->> and assign the Numbering Style to it, the Numbering options are correctly used under the Expected Behavior steps. 

2. If you create a new Paragraph Style, link it to another paragraph style that either: a) has custom indentation options; b) does not use numbering style; the bug will happen, even if you later modify that new paragraph style and link it to <<-None->>. 

3. Therefore, the bug seems to derive from the Custom Numbered Paragraph keeping some options it inherited from the paragraph style it was linked to, even when they are no longer linked.
Comment 2 ign_christian 2014-07-04 05:33:36 UTC
Hello.. Is it still reproduce in LO 4.2.5.2 ?

If problem solved please change status to RESOLVED WORKSFORME, else UNCONFIRMED & provide simple test file along with procedure to see the problem.
Comment 3 QA Administrators 2015-02-19 04:36:48 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2015-04-01 14:51:55 UTC Comment hidden (obsolete)
Comment 5 Regina Henschel 2017-12-09 15:49:50 UTC
The problem is not really solved. I collect related issues in bug 114287.