|
Description
|
Using the sample code from bug #4108907, run the program and do the following:
Click on the menu to pull it down. Click in one of the buttons. Menu will unpost, button will "go down", then (as you release the mouse button) the button will "go up", and it will aquire a highlight (i.e., it is selected). Now, click on the menu again. The menu will pull down, and the highlighted button will unhighlight (as it should). Now (while the menu is down) click in the *other* button. The menu will unpost, the button will go down, then up, then aquire a highlight, just like the other button did before. So far so customer . Now, for the punch line, click on the menu to pull it down again. The menu will pull down, but the highlighted button will remain highlighted.
Via a sequence of events which I can't completely characterize (but which I believe is deterministic and reproducible), it's possible to have both the buttons highlighted, and also have the menu down. Major confusion.
|
|
Evaluation
|
The behavior is no longer exactly as described in the bug report, but it's still broken. In general, there seem to be alot of problems in this area (focus and menus).
xxxxx@xxxxx 1999-09-15
This bug is no longer reproducible after focus management
enhancement putback and will be closed as a duplicate of 4290675
======================================================================
|