Created attachment 165735 [details] Demonstration of field behavior editing numerical numbers SUMMARY (I would assume this is a QT 6 bug, however I don't have the technical understanding to confirm so filing this where I encountered the issue) When editing the Pointer Speed field, and typing in numbers, it changes the number as you're typing, making it difficult to type in a specific number you want. The two scenarios are as soon as you end up with a -0 in the field, it will reset the field immediately back to 0, even if your intent was to change to a different negative floating point 0 number. The second scenario is when adding back a floating point number, the first number you add it will immediately append a zero to, making it difficult to put in the two levels of sensitivity expected in this field. STEPS TO REPRODUCE 1. Open System Settings 2. Select Mouse & Touchpad 3. Select Mouse and choose your mouse device 4. In the Pointer speed text bad, click into the box 5. Delete the last 2 digits (for example, if the number is -0.40, select it and delete the 0 and then the 4) 6. Observe the negative sign is immediately removed from the number, meaning you can't simply type a new number to choose a different negative number if that was your intent. 7. Now, select it and try to change the sensitivity to -0.23 8. Notice when you type in the 2, it immediately appends a zero to become -0.20, so you need to delete the zero to then add the 3 to be become -0.23 OBSERVED RESULT The number in the field is consistently evaluated and overridden by a different value even when the user is actively typing in the field EXPECTED RESULT When I am actively typing in a field, the number should not be changed by the system which interrupts my ability to type the number I want. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.4-arch1-1 EndeavourOS (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION
This appears to be a behavior inherited from the QML SpinBox control that's used there. One would think that keeping its "live" property (https://doc.qt.io/qt-6/qml-qtquick-controls-spinbox.html#live-prop) at its default "false" value would prevent this from happening, and the code for the Pointer Speed control doesn't set it. But alas. Perhaps some investigation on the Qt side is warranted here.
*** Bug 483562 has been marked as a duplicate of this bug. ***