Bug 127751 - Right-click context menu disactivates the very hotkeys (keyboard shortcuts) it shows
Summary: Right-click context menu disactivates the very hotkeys (keyboard shortcuts) i...
Status: RESOLVED DUPLICATE of bug 70063
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.1.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-21 10:54 UTC by munlinux
Modified: 2008-10-04 11:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description munlinux 2006-05-21 10:54:52 UTC 
Version:            (using KDE KDE 3.4.3)
Installed from:    Ubuntu Packages

On KDE Desktop and in Konqueror:
1. Open a context menu by right-clicking on a file.
2. See in the context menu "Rename F2".
3. Press F2.

Result - No response.

There is no reason that the keyboard shortcuts should stop functioning if a context menu is open.
Comment 1 lexual 2006-10-20 02:08:17 UTC 
I can confirm the behaviour, but I'm not sure if it's done deliberately.
Comment 2 FiNeX 2008-06-26 16:34:34 UTC 
This is still valid in KDE4 (dolphin part).

@Peter: sorry if I bother you, do you think this is an intended behaviour of the file manager or does it depends from libs (kde/qt libs) ???? :-)
Comment 3 Peter Penz 2008-06-26 16:42:31 UTC 
@Finex: this depends on Qt and is a common behavior of all GUI-toolkits I know. I just tried how this works on Windows. Here also when a context menu is opened the application shortcuts don't apply.

Whether this is a good behavior or not from a users point of view I'm not sure - I never had the idea to use a shortcut when I've opened a context menu honestly speaking ;-)

So as summary: _if_ this should be fixed it must be done on kdelibs/Qt level, not on application level.
Comment 4 Pino Toscano 2008-10-04 11:34:13 UTC 
Same problem as #70063.

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