Bug 104073

Summary: A Style with DropCap turned on loses the setting after Save and ReOpen.
Product: LibreOffice Reporter: Frank Zimmerman <fz1844>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: fz1844, ilmari.lauhakangas
Priority: medium    
Version: 5.2.3.3 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Shows the loss of DropCaps on custom styles.

Description Frank Zimmerman 2016-11-21 02:28:18 UTC 
Description:
I use DropCaps on my first paragraph and have it set to a custom style. Since the latest upgrade to 5.2.3.3 (on Windows 10 x64), my DropCaps are no longer remembered. When I load the document, the DropCap is turned off.


Steps to Reproduce:
1. Create a paragraph of text (I usually use LinuxLibertine, but tested with Times New Roman as well).
2. Turn DropCap on (I'm using 1 character, 2 lines, 0.02 spacing).
3. Create a New Style with the cursor in this paragraph.
4. Save the document and Close.
5. Reopen the document. DropCaps are not turned on.

Actual Results:  
The DropCap setting is turned off on the specified style.

Expected Results:
The DropCap setting should have been saved with the style.


Reproducible: Always

User Profile Reset: No

Additional Info:
Note, that if I repeat the test without creating a custom style, but just using the "default" style, the DropCap setting IS remembered after save/close/reopen. So it seems to be a problem with custom styles.


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Comment 1 Frank Zimmerman 2016-11-21 02:32:16 UTC 
Created attachment 128898 [details]
Shows the loss of DropCaps on custom styles.

This Document shows the loss of the DropCap setting on Custom Styles. The first paragraph is Default style, and retains the DropCap setting. The second paragraph is formatted with Custom Style "xDropCap", and does not retain the DropCap setting after save/close/reopen.
Comment 2 Buovjaga 2016-11-28 19:51:22 UTC 

*** This bug has been marked as a duplicate of bug 101664 ***