Bug 325893

The accessibility option Sticky Keys in it's default state releases the 'stuck' modifier key after any HID input (mouse click, keyboard non-modifier button pressed). Additionally, Sticky Keys has a Lock feature which does not automatically release the 'stuck modifier', but rather waits until the user presses the modifier key again to release it.

In KDE 4.11 the 'Lock' feature is broken. It is _always_enabled_ for the mouse, and _always_disabled_ for the keyboard, regardless of whether or not the checkbox is checked. Actually, KDE 4.10 had this problem as well, but I though that it was a configuration issue on my part and simply avoided updating to 4.10. However, I can no longer avoid updating and I cannot use current KDE with the Accessibility issue in this state.

What are the conditions for considering an issue high priority? Users with Accessibility issues can no longer use the current KDE, does that quality for high priority?

Reproducible: Always

Steps to Reproduce:
1. Enable Sticky Keys (System Settings -> Accessibility -> Modifier Keys)
2. Enable "Use sticky keys" and disable "Lock sticky keys".
3. In Kate, click Ctrl then click a mail in the Message List Pane to select it. Now click on a second mail and notice that it too is selected. Now a third.
Actual Results:  
All the mails are added to the selection.

Expected Results:  
One would expect that with the "Lock sticky keys" checkbox disabled that the Ctrl button would be released after clicking a single mail. With "Lock sticky keys" disabled the expected workflow to select multiple mails is to either press the Ctrl button after each mail or to hold it down.

Note that this issue affects all modifier keys in all applications. This is most annoying when using Shift- or Ctrl- MouseScroll i.e. in Firefox as the modifier is not release when expected.