When the up/down arrow of a spinner widget is pressed, the new value text is rewritten over the previous one rather than substituting the previous one, so messing up the widget text field and making it unreadable.
Seen with the KDE5 VCL.
Steps to Reproduce:
1. Perform any action that involves a spinner widget (e.g. try to change the position of an object in draw, or to set an option in the options interface)
2. Press the up or down arrow of the spinner widget
New text is written over the old one
New text should replace the old one
User Profile Reset: Yes
[Information automatically included from LibreOffice]
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
The real bug is the now broken native widget support for the ControlType::Spinbox (that's just my guess), at least on kf5. I didn't dig further into it, but did a quick bibisected to:
Author: Henry Castro <email@example.com>
Date: Wed May 6 14:08:07 2020 -0400
lok: fix the window type of the formatted field control
Reviewed-by: Henry Castro <firstname.lastname@example.org>
That looks more like it revealed some underlying bug, probably somewhere in VCL. gtk3 looks ok and didn't need any adaption I could identify in a
git log vcl/unx/gtk3
(In reply to Jan-Marek Glogowski from comment #1)
> The real bug is the now broken native widget support for the
> ControlType::Spinbox (that's just my guess), at least on kf5. I didn't dig
> further into it, but did a quick bibisected to:
> commit 2a694f9e0e7789b4b3b792a9eedd29366fa10c1c
> Author: Henry Castro <email@example.com>
> Date: Wed May 6 14:08:07 2020 -0400
> lok: fix the window type of the formatted field control
> Change-Id: Iab87c94ca19314eacec18e71d7d09ba42f1756e7
> Reviewed-on: https://gerrit.libreoffice.org/c/core/+/93586
> Tested-by: Jenkins
> Reviewed-by: Henry Castro <firstname.lastname@example.org>
> That looks more like it revealed some underlying bug, probably somewhere in
> VCL. gtk3 looks ok and didn't need any adaption I could identify in a
> git log vcl/unx/gtk3
> Very strange.
> CC'ing him.
Closing this as a duplicate of tdf#133498, which I also bibisected to this commit. It's fixed in the meantime.
*** This bug has been marked as a duplicate of bug 133498 ***