Bug 116857 - Footnote Area's Separator Line position is cannot be saved!
Summary: Footnote Area's Separator Line position is cannot be saved!
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-07 03:27 UTC by Munzir Taha
Modified: 2018-04-08 14:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Munzir Taha 2018-04-07 03:27:25 UTC 
Description:
Inserting and footnote and setting the separator line position to right, would display properly until I close the document. When I open the document again, the setting is lost and the position is back to left. I also tested setting it from the page style and still same issue.

Steps to Reproduce:
1. Insert -> Footnote and Endnote -> Footnote
2. Format -> Page, Separator Line: Position: right
3. Save the document, close and re-open.

Actual Results:  
Position: left

Expected Results:
Position: right


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Comment 1 Telesto 2018-04-07 16:33:36 UTC 
No repro - Windows - for me
Version: 6.1.0.0.alpha0+
Build ID: d39a8e791618a40328c0f90bece3cc246dcf57f7
CPU threads: 4; OS: Windows 6.3; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-04-05_23:46:48
Locale: nl-NL (nl_NL); Calc: CL
Comment 2 Munzir Taha 2018-04-07 19:30:17 UTC 
@Telesto: Thanks for testing. Can you confirm whether the bug is fixed in Linux, too?
If you can't, I would wait till there is a release to test.
Comment 3 Dieter 2018-04-08 14:00:49 UTC 
I can remember that this bug was recently fixed. Can you try it with LO 6.0.3?

Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away
Comment 4 Munzir Taha 2018-04-08 14:42:28 UTC 
I now tested 6.0.3 and indeed it's resolved. Thanks