Bug 84877 - In JPEG export, fields coerced to valid values so quickly that it interferes with entry
Summary: In JPEG export, fields coerced to valid values so quickly that it interferes ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Drawing (show other bugs)
Version: unspecified
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-10 16:44 UTC by Luke.A.Somers
Modified: 2014-10-25 14:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Luke.A.Somers 2014-10-10 16:44:39 UTC
Problem description: The coercion of numbers to valid values in the JPEG export form is so quick that it interferes with entering the desired (valid) numbers.

Steps to reproduce:
1. export a drawing as JPEG
2. set the value in this field to 8.5 if it isn't already
3. put the insertion point to the left of the decimal
4. press backspace, then 4 

Current behavior:
the field passes through these states:
0.50
40.50

Expected behavior:
the field passed through these states:
.50
4.50
(note the factor of 9 difference)

Steps to reproduce another example:
5. Put 37 into the pixels/cm field if it isn't already
6. put the insertion point to the right of this number
7. Press backspace twice and then 50

Current behavior:
the field passes through these states:
3
3
35
350
   
Expected behavior:
the field passes through these states:
3

5
50           
(note the factor of 7 difference)
Comment 1 Luke.A.Somers 2014-10-10 16:46:58 UTC
Better yet, instead of entering 50 in step 7, enter 100.

The resulting value is 999 (truncated from 3100) instead of 100.
Comment 2 A (Andy) 2014-10-25 14:24:14 UTC
Strange/Buggy behaviour is reproducible with LO 4.3.2.2 (Win 8.1)

Note: In step 2 the field WIDTH of the JPG OPTIONS dialogue box is mentioned, which is opened after FILE -> EXPORT -> selection of jpg -> pressing the SAVE button.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.