Bug 497085 - Editing values in the Advanced Power Settings SpinBox by clicking between the percent symbol and digits, and then pressing backspace, doesn't work
Summary: Editing values in the Advanced Power Settings SpinBox by clicking between the...
Status: CONFIRMED
Alias: None
Product: frameworks-qqc2-desktop-style
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.8.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-05 14:15 UTC by redford
Modified: 2024-12-16 04:50 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description redford 2024-12-05 14:15:57 UTC
SUMMARY

Editing these percentage text boxes seem literally impossible 🙃

OBSERVED RESULT

E.g., the "Stop charging at" text box:
- I have "97%" there and I want to change it to 95%
- I click with LMB and place the text cursor after digit "7"
- I press backspace to erase "7" (with the intention to type "5" afterwards)
- Now both "Stop charging at" and "Stop charging once below" both jumped to "50%" and my cursor moved after the %" sign (???)
- I have to struggle a lot doing random edits and changes to be able to enter the intended value there.

EXPECTED RESULT

Make it possible to edit :)

SOFTWARE/OS VERSIONS

KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel: 6.12.1-arch1-1 (64-bit)

ADDITIONAL INFORMATION
Comment 1 Kai Uwe Broulik 2024-12-05 15:49:53 UTC
Yeah the qqc2 SpinBox is quite peculiar... re-assigning
Comment 2 John Kizer 2024-12-16 04:50:40 UTC
I don't have a device that supports "Stop charging at", but I can reproduce that it's difficult to edit the numbers in the other spinboxes on that page using the "click before the % and backspace" method you described, which is how I would also normally try to set a precise number there.

For devs - this isn't about the Pointer Speed use of the control, but is this fundamentally the same issue as https://bugs.kde.org/show_bug.cgi?id=481187 ?