https://bugs.kde.org/show_bug.cgi?id=524354
--- Comment #3 from [email protected] --- Hi, Thanks so much for working on these CapsLock issues. As a screen reader user, I really appreciate it. This bug is different than #524098. Bug 524098 involves CapsLock getting stuck in the on position. This bug relates specifically to CapsLock getting toggled on/off when it shouldn't be. Sorry for the confusion with two similar bugs. The issue captured in steps 4-5 of this bug is that when a user performs an Orca command like CapsLock+t, the press of CapsLock used in the command to speak the time counts towards the first press of two presses in Kwin to toggle the CapsLock state, so if they press Capslock again quickly after releasing the keys, CapsLock will be toggled on. I would expect a CapsLock press to count toward the two-press toggle only when CapsLock is pressed and released without any additional keys being pressed while CapsLock is held down. In other words, a CapsLock press that is part of an Orca command should not count toward the two-press toggle that changes the CapsLock state. You have to be quick to reproduce this, because the second press of capslock must be within the keyboard repeat delay time. Reproduced in KDE Linux 202609141616. -- You are receiving this mail because: You are watching all bug changes.
