There are a number of non-intuitive behaviours that I believe the XP menus currently exhibit. They aren't critical, but I believe they might prove to be a minor annoyance at some times: 1. When the application with the menu loses focus and the menu is displayed, the menu must disappear. 2. Clicking the mouse anywhere off the menus should cause them to disappear. 3. Holding the left mouse button while selecting a top-level menu (ie: "File") should put the menu into "wait for mouse button release" mode, ie: select the subitem under the cursor when the mouse button is released (or clear the menu if no item is under the cursor). If the mouse button is released over one of the top level menu items, a disabled menu item or a seperator bar, the menu should stay up and wait for a click to select the item. Windows handles this in a fairly decent manner. When the user depresses the left mouse button anywhere on a space currently displaying menu items (ie: the menu bar, popup menus, etc.), the menu is put into an active state. Releasing the mouse button over top of any selectable item will then trigger it. Releasing the mouse button over a popup menu item parent will open the popup menu immediately. With this system, a single click to select a menu item is acutally just a click/release combo without any mouse movement inbetween. 4. Clicking the mouse on a popup menu item's parent should display the popup menu immediately (instead of the small but perceptable delay)

One defect to a bug report, please. Phillip, could you factor this out into multiple reports, and weed out any dups?

sure, i'm on the case...

1. is new. mouse clicks are not the only way for a menu to lose focus. (alt-tab, command-tab, new apps appearing, system alert dialogs, etc.) 2. is a duplicate of bug 11137 3. is new, and because of the long description in this report, this bug will become item #3. 4. is a performance bug. i'll open it. this is what i propose. this bug becomes only item #3 [xpmenu: click-drag-release out of menu leaves menus visible], change summary as appropriate. i'll open up items 1 and 4 and note them here for posterity.

#1. is now filed as bug 11343 (click/release) #4. is now filed as bug 11345 (performance)

assigning to hyatt as p2 for m10

The issue with being able to hold the mouse down and move around in the menus has been resolved, so I'm marking #3 fixed.

I think that this bug might actually still exist. To reproduce it, you can grab yesterday's Win32 build and do the following: 1. Click on the File menu with the left mouse button and hold it down 2. Drag the mouse down, past the bottom of the menu and release the mouse button The expected behaviour is that the menu should disappear (try a native menu). Releasing the mouse button anywhere on the screen that isn't in a menu should cause the menu to disappear to be consistant with the native Win32 menus. I think this bug should be reopened.

Oh, ok, that's what you're talking about. I already have a bug about that, so this one doesn't need to be reopened.

doing the right thing by changing this to a dup of (presumably) bug 11266

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

marking verified, will add mmastrac@ucalgary.ca to the cc list for 11266