Issue 125805 - Table Properties| Sofware crashes if calculation of table width is not complete when "spacing" is updated to a value greater than table width
Summary: Table Properties| Sofware crashes if calculation of table width is not comple...
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 4.1.1
Hardware: PC Windows 7
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-29 22:25 UTC by Amanda Anderson
Modified: 2014-10-30 08:43 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Table Properties (77.43 KB, image/jpeg)
2014-10-29 22:32 UTC, Amanda Anderson
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Amanda Anderson 2014-10-29 22:25:56 UTC
Overview:  When a number greater than table width is entered in Left Spacing text box and alignment is set to "Center", the application will crash/close unexpectedly if focus IS NOT taken off the Left Spacing text box when Ok button is pressed.  
  
Steps to Reproduce:
  
1. Add a table to Writer
2. Open the Table Properties
3. Select Center for Alignment
4. Check Relative beside the width text box and set it to 80%
5. Enter 90% in the Left Spacing text box (Do Not Press Tab button)
6. Press OK

Actual Results: Software will crash/close unexpectedly

Expected Results: I expect it to act the same way it does if focus is taken off the text box before the Ok button is pressed.  If focus is taken off the text box, the the calculation is adjusted to best case.

Build date & Hardware: 
Build 2014-09-13 on Windows 7 Professional
Comment 1 Amanda Anderson 2014-10-29 22:32:46 UTC
Created attachment 84120 [details]
Table Properties
Comment 2 oooforum (fr) 2014-10-30 08:43:43 UTC
If I use spin button to increase "Left spacing" value, I can't go beyond 50% because table width can't decrase under 1%. 

I confirm the crash but for me, the input value must be coherent.
Clearly, the developer does not expected this kind of behavior.