Created attachment 176068 [details] showcase SUMMARY Clicking Reset button highlights (selects) Defaults button STEPS TO REPRODUCE 1. Open random KCM 2. Change some settings 3. Click Reset button -> Defaults button is highlighted (selected) OBSERVED RESULT Clicking Reset button highlights (selects) Defaults button EXPECTED RESULT Clicking Reset button highlights (selects) Defaults button SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.9-arch1-1 (64-bit) Graphics Platform: Wayland
Hi - could you please clarify what your Expected Result is? As written, it's identical to the Observed Result, which would seem to mean something that's working as intended?
Yeah, sorry. I made a mistake. Here it is again: OBSERVED RESULT Clicking Reset button highlights (selects) the Defaults button EXPECTED RESULT Clicking Reset button DOESN'T highlight (select) the Defaults button
Ah OK - and sorry, for my own knowledge, why is that not desirable behavior?
Hmm, can't really put it into words, but it's not logical to me. Reset and Defaults are 2 different buttons that although do similar things, aren't linked in any way. The workflow here is: User changes something and doesn't like the change so he clicks the reset button and done. No extra action is needed here. It's not a workflow where user is REQUIRED to click Reset and then immediately Defaults (where you could argue we're assisting user on future action after Reset button) although that's still a valid set of actions.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Hey John, what do you think, is this a legit bug? User changes something and doesn't like the change so he clicks the reset button and done. No reason the Defaults button needs to be highlighted.
I think someone else would need to decide that one. If it were just my perspective - if I were using the keyboard to maneuver around, I would actually want a clear highlighted button to remain after using a button that becomes disabled after its use. Without that, it's easier for me to be lost in where the active button is and where I'll likely go next when trying to tab through options. So I would perceive the current state as a feature, not a bug (no joke intended :-) ), and changing to no buttons being activated as making it harder for keyboard users. But I'm not a designer or UI/UX person by any stretch of the imagination!
Okay, thanks for the help.
Indeed, this is a feature, for the reason that John indicates!