JDK-6246541 : Regression: incorrect Java IMF/SPI behavior from mustang b28
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt:i18n
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Incomplete
  • OS: solaris
  • CPU: x86
  • Submitted: 2005-03-28
  • Updated: 2020-11-03
  • Resolved: 2013-06-25
Related Reports
Relates :  
JDK-6247108 - Native input method is not deactivated when switching to java input method
Relates :  
JDK-4425917 - Merlin : Input method switching does not work well in Solaris and x86 solaris
Description
After switching from native to Java IM, input method doesn't accept inputs. Reproducible on Solaris platforms.

testcase:
/java/j2se-sqe/i18n/workspaces/i18n_mustang_ws/i18n/bundles/b01/IMF-b01.zip

to reproduce:
Obtain and expand above test case. It's actually a tar file.
Go to i18n/src/IMF directory.
perl runit.pl -TEST SPIQL -TOOLROOT . -JAVAHOME $JAVA_HOME -LOCALE ja 401.
Follow the test instruction, you'll see that you won't be able to input any characters correctly with Wubi input method. It works fine on Motif mode.

This testcase works well on Mustang b27.

###@###.### 2005-03-28 01:56:36 GMT
###@###.### 2005-03-29 18:20:35 GMT
Comments
Could not locate the test case. Please reopen this with the test case attached.
25-06-2013
EVALUATION Couldn't reproduce this bug on Solaris 9 using the testcase from comments section.
16-11-2005
EVALUATION Regarding last evaluation, in fact, 6214521 is only reproducible on Solaris 10, I believe this bug is reproducible on Solaris 9 as well, so I don't think this might relate to bug 6214521.
15-11-2005
EVALUATION I could reproduce this bug after the submitter comments. I inserted the logging to verify that key events comming from the X server. On XAWT it happens that there is no key events is triggered by the X server. At the same time, on Motif it works. Perhaps, the bug 6214521 (deactivating the native input method fails) is related to this issue somehow. It's interesting that the bug 6246541 is reproducible only if deactivating the native input method happens. Will investigate further.
14-11-2005
EVALUATION Asked the customer about aditional information.
18-10-2005
EVALUATION No that is not the problem. Please assign key for IM selection and use it by following procedure described in 5049524 description. It's reproducible on Solaris 10 3/05 s10_74L2 SPARC, JDS, ja_JP.UTF-8.
17-10-2005
EVALUATION Actually these problems start to show after the switch to XAWT around b28. It works fine in motif mode (you can pass -JAVA_FLAG -Dawt.toolkit=sun.awt.motif.MToolkit to the "perl runit.pl" command mentioned in the bug description) even with the latest build. I believe these are key mapping related issues since whatever I typed is totally messed up. Reassign to AWT folks for further investigations. ###@###.### 2005-03-28 20:35:37 GMT Mustang PIT b39 testing results. As far as I see, it is possible even with CDE to obtain some resonable results if you click back and for preventing "unfocusable" status & IM windows from grabbing focus. Everything works under Linux (SuSe 9.2 + KDE) and Solaris10+JDS3 (Gnome). The only problem I found is with CDE when, after popping, WuBi input method candidate window which supposed to be unfocusable does grab focus. Result is, no visible keyboard response until one explicitly changes focus to active client component. That is a known bug with CDE. ###@###.### 2005-05-31 10:27:11 GMT As you can see from descrition: "you won't be able to input any characters correctly with Wubi". Actually, I couldn't choose the Wubi input method using the menu of the frame because there is no any 'Set input method' menu item. It's reproducible on XToolkit, SunOS colorado 5.10 Generic sun4u sparc SUNW,Sun-Blade-100. I could reproduce this bug using Mustang b27 as well. Could you please confirm that this is the actual problem? Could you please provide more information about OS/version as well? I'm changing the status to incomplete/need more info until any additional information about the bug is provided.
28-03-2005