On the _URL_ open one of pull-down menus, then click on another pull-down menu. For me it closes the opened menu, but doesn't open the menu I click - just highlights the pull-down icon. Using build 021708 on Windows 98 SE.

Reassigning to Rod.

Confirmed with 2000-02-17-08-M14 on Windows NT 4.0 Same result seen with NN 4.7 on Windows NT 4.0 This same issue applied to Mozilla's own menus, rather than <SELECT>s in a form, is the subject of bug 28086, "two clicks required to pick different menu on toolbar", M16. But I think pinkerton@netscape.com would argue that only true menus, and nothing else, should be activated by the same click that dismisses a menu, so this report may share more kinship with bug 21390, "Clicking on Widget or link does nothing if menu open", M15, ASSIGNED to german@netscape.com for a decision on how that should work. Personally I don't like the insconsistency of sometimes one click, sometimes two, depending on whether a menu is active. I believe Pinkerton is looking at this from the other end: sometimes a click only dismisses a menu, sometimes it does that and something else, depending on where it lands. I'd argue that it makes more sense to have consistency based on where the mousing is going, not where it came from, but just as strongly that whichever is chosen should apply universally, including Form Controls, in order not to be confusing.

Would you want to click a button in the content area that pops up a menu (such as the attachment button) when trying to dismiss a menu and have it popup its menu? I just wanted to dismiss the stupid menu. Having some things accept the click and others not is just plain confusing. My opinion is that nothing should take that click except very possibly popups in the same bar, but even that is full of peril as what do you do when you click on something that is the bar but doesn't have a popup? No decision we make can be right in all cases. Something is seriously wrong here.

This is native MS-Windows behavior, when a combobox is droppeddown and another combobox is clicked on the first dropdown rolls up and the click on the new combo is "eaten" This behavior is correct - marking invalid

We can easily configure it. It is a cal you make when you register your roll up. Right now combobox eat the event and menus do not. If you want to discuss the menu not-eating issue talk to Hyatt.

Updating QA contact.

This is how it is supposed to work. No arguments here tried in Netscape & IE both work the same way. Marking as Verified.