-
Bug
-
Resolution: Unresolved
-
P4
-
None
-
1.4.0
-
x86
-
windows_xp
Disabled components should not respond to user interactions and should not trigger any events. But a disabled choice triggers MouseExited event after it is disabled and when mouse is taken out of the disabled component. This is seen right since 1.4 only on win32 platform.
I have attached a sample test. Execute the sample test. Keep the mouse inside the choice component. Press 'TAB' and move the focus to button. Press 'SPACE BAR'. The button will be pressed and this would disable the choice. Now move the mouse. You would see a MouseExited event being triggered by Choice.
###@###.### 2005-04-08 09:24:17 GMT
I have attached a sample test. Execute the sample test. Keep the mouse inside the choice component. Press 'TAB' and move the focus to button. Press 'SPACE BAR'. The button will be pressed and this would disable the choice. Now move the mouse. You would see a MouseExited event being triggered by Choice.
###@###.### 2005-04-08 09:24:17 GMT
- relates to
-
JDK-6190728 Non focusable choice is unusable on win32
-
- Closed
-