Bug 125825 - Unable to disable AccessKeys
Summary: Unable to disable AccessKeys
Status: RESOLVED DUPLICATE of bug 124218
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-18 19:28 UTC by Christoph Wiesen
Modified: 2006-04-18 19:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Wiesen 2006-04-18 19:28:04 UTC
Version:           3.5.2 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu6 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-20-386

KDE 3.5.x brought a new feature that wasn't there (at least in this form) in 3.4 called "AccessKeys" I assume (the setting to disable them is called that way).

The feature I'm talking about is available when Konqueror is displaying a website. You have to shortly push Ctrl and release it again - then small tooltips with different keys from  A - Z will show up all over the website currently displayed. If you now press one of those keys the associated link will be followed. This has the potential to unwillingly lead to to a website and interrupt your workflow if not loosing actual work you did on the previous page.

Ctrl is for example used to quickly switch between desktops or is used for many other actions, like copy/paste. I use these functions a lot. But since I'm still a human I happen to hold down ctrl without actually pressing another key then - so the mentioned tooltips will come up.

Another scenario is that a user wants to copy some text (ctrl+c) but accidentally lets go of ctrl to early and thus will active the link that's associated with "c" (just an example - ctrl is used as a modifier with all kinds of keys) will be opened, leaving the user with a completely unexpected change of website.

Those use cases probably recommend not to have this kind of "Access Keys" by default at all - they should be available from within the Accessibility options within KControl.

Anyway there actually is no obvious way to get rid of them - no option to disable this feature. I would have expected this feature to be gone when I disabled "Sticky Keys" from within "Accessibility".

The solution I found was to manually edit a config file. This I found in the blog of KDE dev zander:
http://www.kdedevelopers.org/node/1569

Please have a look there for further evaluation of "Access Keys" and why it might actually hurt usability.
Comment 1 Tommi Tervo 2006-04-18 19:49:45 UTC

*** This bug has been marked as a duplicate of 124218 ***