Comment 44 for bug 996801
Revision history for this message
|
|
#44 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #12)
> It seems extremely obvious to me that this accessibility requirement should not
> be disabled by default.
It may be obvious for "desktop environments". But I would have thought that the users of this accessibility feature (mis-feature for those who don't need it) always are under a desktop environment, so that it would be fine to disable it by default everywhere else. I'd like to hear how this feature is used in practice (when, how often, etc.). Wouldn't the system be able to guess whether SlowKeys should be activated or not when Shift is held for 8 seconds (i.e. whether it is intended to activate SlowKeys or not)?
It seems that I sometimes hold Shift without doing anything else, just because I intend to type PageUp/PageDown once I've finished to read text. So, fixing the problem for mouse actions would not be sufficient. IMHO, SlowKeys shouldn't be activated in the case another key is pressed while Shift is still held, i.e. SlowKeys could be activated at the Shift Key Release event if pressed for at least 8 seconds (not once the 8 seconds have elapsed like now), only when another key hasn't been pressed and the mouse hasn't been used between the key press and the key release.