[Mono-bugs] [Bug 81509][Wis] New - NullReferenceException in System.Windows.Forms.MenuTracker.Deactivate()

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tausq at debian.org.

http://bugzilla.ximian.com/show_bug.cgi?id=81509

--- shadow/81509	2007-05-01 13:34:12.000000000 -0400
+++ shadow/81509.tmp.18956	2007-05-01 13:34:12.000000000 -0400
@@ -0,0 +1,43 @@
+Bug#: 81509
+Product: Mono: Class Libraries
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: ubuntu
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: toshok at ximian.com                            
+ReportedBy: tausq at debian.org               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: NullReferenceException in System.Windows.Forms.MenuTracker.Deactivate()
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Deactivating the default textbox popup by clicking outside the popup causes
+a NullReferenceException in some cases.
+
+Steps to reproduce the problem:
+1. Compile and run the testcase
+2. Right click on the textbox to bring up the context menu
+3. Move your mouse so that one of the menu items is highlighted (but no
+need to click it)
+4. Click outside the context menu to deactivate the menu
+
+Actual Results:
+NullReferenceException at System.Windows.Forms.MenuTracker.Deactivate()
+
+Expected Results:
+Context menu disappears, app continues to run
+
+How often does this happen? 
+Always reproducible using the steps above, but if no menu items in the
+popup were highlighted prior to clicking outside the popup, the crash does
+not occur
+
+Additional Information: