-
Bug
-
Resolution: Not an Issue
-
P4
-
None
-
6
-
generic
-
linux
I'm using XToolkit with JDK6.0b25.
I have two java.awt.Choices. One of them is focusable another is UNfocusable. When I open unfocusable choice and press key down on my keyboard I could see that KeyEvents are delivered to focusable Choice (it is now has focus).
When I use Motif instead of XAWT I could see that unfocusable Choice changes their value in opened menu below it. This is inconsistence between toolkits.
Should modify XAWT behaviour and make it as Motif's.
Run J2 test from Comments section. You would see two Choices: up(unfocusable) and bottom (focusable)
Open first one and press Down button on your keyboard. If you see that second Choice changes its value (without opening) the bug reproduced.
###@###.### 2005-03-03 13:51:09 GMT
I have two java.awt.Choices. One of them is focusable another is UNfocusable. When I open unfocusable choice and press key down on my keyboard I could see that KeyEvents are delivered to focusable Choice (it is now has focus).
When I use Motif instead of XAWT I could see that unfocusable Choice changes their value in opened menu below it. This is inconsistence between toolkits.
Should modify XAWT behaviour and make it as Motif's.
Run J2 test from Comments section. You would see two Choices: up(unfocusable) and bottom (focusable)
Open first one and press Down button on your keyboard. If you see that second Choice changes its value (without opening) the bug reproduced.
###@###.### 2005-03-03 13:51:09 GMT
- relates to
-
JDK-6354096 REG: Non-focusable choice responds to keyboard inputs when drop-down is active, XToolkit
-
- Closed
-
-
JDK-6275110 PIT. Choice does not trigger key events when drop down visible
-
- Closed
-