Bug 118715

Summary: The effect of editing the spacing in the table Proporties dialog difference between manual input and using the up/down buttons
Product: LibreOffice Reporter: Telesto <telesto>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: dgp-mail
Priority: medium    
Version: 6.1.0.1 rc   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=118716
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Example file

Description Telesto 2018-07-12 09:42:45 UTC 
Description:
The effect of editing the spacing in the table Proporties dialog difference between manual input and using the up/down buttons




Steps to Reproduce:
1. Open Writer
2. Open the attached file (normal view)
3. Open table properties -> Table tab (for the main table)
4. Choose Alignment Left
5. Enter spacing right -2.70 (by typing into it pressing OK/Enter
6. Undo CTRL+Z
7. Repeat 3-5. But don't type =2.70 into the field but use the down button
8. Notice the difference & that the inner border of the embedded table can't be moved
9. Save the file & reload -> notice a layout change

Actual Results:
The effect of editing the spacing in the table Proporties dialog difference between manual input and using the up/down buttons

Expected Results:
Should be the same


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.2.0.0.alpha0+
Build ID: bb1d5780226bb1b9156580972eea9aa849178742
CPU threads: 4; OS: Windows 6.3; UI render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-07-03_05:56:48
Locale: nl-NL (nl_NL); Calc: CL
Comment 1 Telesto 2018-07-12 09:49:01 UTC 
Created attachment 143502 [details]
Example file
Comment 2 Dieter 2018-07-14 06:34:30 UTC 
I couldn't see any difference

Version: 6.2.0.0.alpha0+ (x64)
Build ID: b0e291a7efcd3af2a72d0b622b1f1b84723f011f
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-06-30_23:43:40
Locale: en-US (de_DE); Calc: CL
Comment 3 Telesto 2018-07-16 16:51:46 UTC 
Probably a profile error