JDK-6311415 : Deactivate the input method is not necessary when input method is null
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt:i18n
- Affected Version: 6
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-08-16
- Updated: 2010-04-02
- Resolved: 2005-09-12
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b52Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
sun.awt.im.InputContext.disableNativeIM implementation tries to call "getInputMethod()" to get the input method instance which calls the native im server to create an input method object. This is not necessary since the disableNativeIM should be no-op when the current input method hasn't been created yet.
Comments
|