JDK-4204543 : Composed text not committed when switching input method from menu
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt:i18n
  • Affected Version: 1.2.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_2.5.1
  • CPU: generic
  • Submitted: 1999-01-20
  • Updated: 1999-11-03
  • Resolved: 1999-06-08
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
1.3.0 betaFixed
Related Reports
Relates :  
Description
Run test/java/awt/im/IMFTest on Japanese Solaris with IIIMP enabled. Click into the active or passive client to activate it. Type Control-Space to turn on the input method, type a syllable, say, "ni". Pull down the system menu, choose the last item to bring up the input method selection popup. Choose "Network input method Japanese". Notice that the text component no longer has the focus, but that the syllable typed with the previous input method is still highlighted. Click into the component to reactivate it. Type Control-Space to turn on the input method, type a character, say, "h". The new character replaces the existing syllable.

What should have happened: When the new input method was selected, the existing composed text should have been committed. Text typed with the new input method should be appended to the previous text, not replace it.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel FIXED IN: kestrel-beta INTEGRATED IN: kestrel-beta
14-06-2004

EVALUATION sun.awt.im.InputContext.changeInputMethod calls endComposition if there is a current client, but thanks to Motif's bizarre focus behavior the real current client has lost the focus. Looks like we need to look at the previous client component just like in activate. This may be tricky because changeInputMethod is called on a different thread. This bug should be fixed along with 4116598. norbert.lindenberg@Eng 1999-01-20 This has been fixed as a side effect of the input method engine SPI development. norbert.lindenberg@Eng 1999-06-08
20-01-1999