-
Bug
-
Resolution: Fixed
-
P3
-
5.0, 6
-
b48
-
x86
-
linux, linux_sun
-
Not verified
Toolkit.getLockingKeyState() is supposed to return the ststus of CAPS Lock, Num Lock and Scroll lock keys when called with respect to those key codes. This is supported on Motif and works fine on Motif. But with XToolkit, this method is throwing an unsupported operation exception. Though this exception is documented, this behavior is not compatible with previous releases since XToolkit is the default toolkit on linux since tiger. This must be supported on XToolkit which otherwise would appear as a regression in linux on tiger.
This is reproducible with XToolkit on Linux and Solaris10. This is not reproducible on win32. This is not reproducible with JDK 1.4.2 on linux.
I have attached a sample test. Execute the sample test. You would see a frame with a button. Click on the button. If an UnsupportedOperationException is thrown, the bug is reproduced.
This is reproducible with XToolkit on Linux and Solaris10. This is not reproducible on win32. This is not reproducible with JDK 1.4.2 on linux.
I have attached a sample test. Execute the sample test. You would see a frame with a button. Click on the button. If an UnsupportedOperationException is thrown, the bug is reproduced.
- duplicates
-
JDK-4834514 Toolkit.getLockingKeyState doesn't work with XKB enabled.
-
- Closed
-
- relates to
-
JDK-6446665 java.awt.Toolkit setLockingKeyState
-
- Open
-