I have a list with 15 items. The second item in the list is selected. When clicking a button, I am calling list.deselect(14). This should actually be ignored since item-14 is not selected. But calling this method de-selects the currently selected item in the list. Calling deselect() always de-selects the currently selected item regardless of the index specified.

This is reproducible only on Win32 since 1.4.2 (occuring on Tiger, Mustang as well). Not reproducible on XToolkit.

I have attached a sample test. Execute the test on WinXP. The third item in the list must be shown as selected. Click the button located next to List. This would actually call deselect(14). If you see item-3 being deselected and 'null' printed on the console (selected item) the bug is reproduced.
###@###.### 2005-03-30 15:13:53 GMT