The ContextMenu is closed on the MouseLeftButtonDown event, this appears to be inconsistent with standard contextmenu behaviour where the contextmenu is closed on the MouseLeftButtonUp event. I encountered a lot of pain recently due to this behaviour: When the contextmenu is closed on the mousedown event the corresponding mouseup event is then captured by the associated control for that contextmenu and if this control implements a Click event it causes false positives to invoke the click eventhandler.
The result is that the context menu handles the mousedown event but the corresponding mouseup event (when releasing the mouse button) is then handled by the associated control, because the context menu has been closed. I believe this is a bug with the context menu control.
Comments: ** Comment from web user: korisu **
The result is that the context menu handles the mousedown event but the corresponding mouseup event (when releasing the mouse button) is then handled by the associated control, because the context menu has been closed. I believe this is a bug with the context menu control.
Comments: ** Comment from web user: korisu **
Seconded. This is causing all sorts of issues with context menus and underlying controls for us. While I believe that this is more than partially due to either Silverlight's or other products' implementations of the Click event (which should track both the mousedown AND the mouseup, not just the mouseup), this issue could have been easily avoided by simply handling the mouseup for the context menu items instead of mousedown. Please put a ClickMode property (like the one from ButtonBase) on MenuItem so that we have at least _some_ degree of control over this!