JDK-7048177 : Korean IME's Hanja candidate window not visible and input area goes to (0,0)
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2011-05-25
  • Updated: 2018-09-05
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-7045354 - Korean IME's Hanja candidate window is not displayed on IMFDemo
Description
AWT TextField Korean input seems broken in jdk7 (although fixed in Swing with 7045354).
I've observed described below on Windows XP sp3.

(1) Take an AWT test containing just a Frame with a TextArea, compile and run.
(2) Switch to Korean.
(3) Change Hangul mode in IME's language bar.
(4) Start typing "gks"
Now,
(4.1) in pre-b55 builds, say b51, you'll see a blinking ideogram in inverse colors just here at the caret position (see an attached image)
(4.2) in post b55 builds, say b140, the ideogram will be visible on the gray background at (0,0) -- again see another attached image.

In both cases (and with a special build provided for 7045354 as well) there will be no candidate window. If you press a number, 1 or 2, a correspondent candidate will be committed.
Comments
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
- this is an issue reported against 7(7u), - there are now affected version 9 filed for this issue - 7u issues are transferred to Sustaining Nevertheless if someone have a report against 9 - please reopen and add affectedVersion 9 or 7u specific escalations might be reopen to Sustaining
10-08-2014
EVALUATION The problem is reproducile on Ubuntu 10.4 (dual-screen env.)
25-05-2011
PUBLIC COMMENTS Oops, the issue is not so serious after all: with a fix to 7045354 we actually *have* the candidate window -- it's just in remotest SouthEast corner of a display. Thus the problem is just in coordinates and, in my opinion, it may wait until 7u or 8.
25-05-2011