Bug 51317 - Menus are too sticky
Summary: Menus are too sticky
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdebase   
(Show other bugs)
Version: roswell
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-09 13:10 UTC by Mark H Johnson
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-09 13:10:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Mark H Johnson 2001-08-09 13:10:48 UTC
Description of Problem:
Not sure why, but the behavior of menu selections from KDE's panel is now
pretty user hostile. A selected menu used to disappear when you moved away
from it. Now - if a sub-menu is displayed, the menu stays up "forever" [or
at least until you click on the main menu or the item that caused the menu
to pop up in the first place.

How Reproducible:
Select a menu (e.g., Internet) with a submenu. Display the submenu. Move
the mouse away & work with other windows. The menu stays up.

Steps to Reproduce:
1. Select the "K" logo on the right side of KDE's panel. 
2. Select a submenu (e.g., Games).
3. Click on another window & keep working. The menu stays up and often
blocks your view of the area you are working in.

Actual Results:
Menu displays long after you are "done" with it.

Expected Results:
Menu disappears when you move "too far" away (the 7.1 behavior).

Additional Information:
If there is a setting for this [and/or a help guide I should have found],
please let me know.

Comment 1 Bernhard Rosenkraenzer 2001-08-09 13:17:04 UTC
This behavior was needed for technical reasons when we added the tear-off 
possibility to the menus.
The code will probably be changed to allow the old behavior along with 
tear-off menus in the KDE 3.0 timeframe.

Note You need to log in before you can comment on or make changes to this bug.