Bug 107879 - Draw should not prepend a decimal ,xx value with zero without leaving the input field
Summary: Draw should not prepend a decimal ,xx value with zero without leaving the inp...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
5.3.1.2 release
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-15 20:11 UTC by Roland Illig
Modified: 2023-05-20 04:59 UTC (History)
2 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 Roland Illig 2017-05-15 20:11:49 UTC 
Description:
When editing the properties of a drawing object, I want to type numbers like in other text fields. Instead of letting me edit my numbers, Draw automatically "corrects" them on the fly, leading to wrong numbers.

Steps to Reproduce:
1. Create a new drawing document.
2. Add a rectangle, approximately 5 times 5 cm.
3. Open the properties, focus the X position, place the cursor at the very left.
4. Delete the digit before the comma, wait a bit.
5. Type the number 7.

Actual Results:  
The X position of the rectangle is now 38.00 cm, although I neither typed a 3 nor an 8.

Expected Results:
The X position of the rectangle is now 7.xy cm.


Reproducible: Always

User Profile Reset: No

Additional Info:
Because of Draw's behavior of getting into my way, I cannot edit my document as I want, since I constantly need to re-check on the screen whether Draw still does what I want or whether it disturbs me.


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Comment 1 Eike Rathke 2017-05-15 21:14:38 UTC 
Note that if you wait between deleting the last digit before the decimal separator (which leaves input field as ,xx) and typing another digit, a 0 is prepended to form the input value 0,xx; then typing a 7 yields 70,xx that is an X offset too large to position the object, hence gets adjusted to the maximum positionable offset, in your case 38,00

To prevent premature positioning of 0,xx you can either select the digit you want to replace (i.e. 5) and then type the digit you want, or if the 0 was already prepended delete it and it will not be prepended again.
Comment 2 Roland Illig 2017-05-16 05:22:18 UTC 
This workaround is not acceptable to me.

Draw should follow this general principle:

    When the user types something while not looking at the screen,
    the program must interpret the key sequence as-is.

This means that at least, when automatically inserting a zero, this zero must be selected so that when I type a 7 later, it is overwritten.
Comment 3 Buovjaga 2017-05-22 15:57:06 UTC 
I don't get the 0 by simply waiting. I have to switch to another program and back. I even washed the dishes while waiting and it did not change.

This behaviour is unintuitive and should be changed -> NEW

Version: 5.4.0.0.alpha1+
Build ID: c90510acfe1ec042adf27452e311964a770965a6
CPU threads: 4; OS: Windows 6.2; UI render: default; 
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-13_21:42:54
Locale: fi-FI (fi_FI); Calc: group

Arch Linux 64-bit, KDE Plasma 5
Version: 5.5.0.0.alpha0+
Build ID: 6b5fc059543c16759abd5eec2576b5b68e96883a
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 21st 2017
Comment 4 QA Administrators 2018-05-23 02:35:52 UTC Comment hidden (obsolete)
Comment 5 Rodolfo 2018-08-11 18:08:50 UTC 
@Buovjaga , so the current behavior is: when numeric input field begins with ","  and it looses focus, preppend it with '0'.

What should be the correct behavior?
Comment 6 Buovjaga 2018-08-16 18:50:53 UTC 
(In reply to Rodolfo from comment #5)
> @Buovjaga , so the current behavior is: when numeric input field begins with
> ","  and it looses focus, preppend it with '0'.
> 
> What should be the correct behavior?

I cannot repro the behaviour I reported in comment 3 anymore, so the current behaviour is the same as reported by Roland and Eike.
Comment 7 QA Administrators 2019-08-19 07:00:38 UTC Comment hidden (obsolete)
Comment 8 Roland Illig 2019-08-19 18:24:27 UTC 
Still reproducible and relevant.

Version: 6.3.0.4 (x64)
Build-ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU-Threads: 8; BS: Windows 10.0; UI-Render: GL; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: CL

Instead of 38,00 cm the X position becomes 33,00 cm, but apart from that it's still the same.
Comment 9 QA Administrators 2021-08-19 03:43:41 UTC Comment hidden (obsolete)
Comment 10 BogdanB 2023-05-19 18:09:32 UTC 
Please retest.
Comment 11 Roland Illig 2023-05-19 23:30:24 UTC 
Successfully retested with 7.5.3.2, thanks for fixing this particular UX problem.

While testing, I found 10 other problems. Should I report them as well, or do you already have enough bug reports for now?
Comment 12 BogdanB 2023-05-20 04:59:35 UTC 
> While testing, I found 10 other problems. Should I report them as well, or
> do you already have enough bug reports for now?

If you have time to report each of the 10 problems individually, you can do that. Before reporting bugs, it would be much safer to do a reset to factory settings in order to be sure that the problems you see are not solved, but unseen, because of a corrupt user profile. Factory Reset: Help - Restart in Safe Mode - Restart - and check the 2 options from Factory Settings. If the bugs are still there, before reporting you can try to search for existing bugs, then, if not already reported, you could report them.

If you mixed them in one bug, the bug will be closed.