|Summary:||[IM]The composition mode gets lost when focus traverses|
|Product:||Red Hat Enterprise Linux 3||Reporter:||Xiaobin Lu <xiaobinlu02>|
|Component:||openoffice.org||Assignee:||Caolan McNamara <caolanm>|
|Status:||CLOSED NEXTRELEASE||QA Contact:|
|Fixed In Version:||1.9.121-3||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-04-12 07:59:45 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Xiaobin Lu 2005-07-14 17:39:31 UTC
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Description of problem: For any application, for example, Openoffice.org Calc, if you enable japanese input in one text field and move the focus to another text field, you need to enable japanese input again in order to input Japanese. This bug won't be seen in Advanced server 2.1. Version-Release number of selected component (if applicable): kinput2-canna-wnn6-v3.1-12.EL How reproducible: Always Steps to Reproduce: 1. Open Openoffice.org Calc 2. Focus the keyboard input on the top textfield and enable japanese input, type "ka", you will see it gets converted to japanese character, press enter. 3. Move the focus to another text field, type "ka", you will see the English "ka" character Actual Results: Actual "ka" is displayed Expected Results: You should see "ka" converted to japanese character Additional info: Not reproducible with Chinese, Korean input method. Not reproducible with Advanced Server 2.1
Comment 1 Akira TAGOH 2005-07-19 02:33:03 UTC
This is not a kinput2 bug because it's technically caused by OOo has the different Input Context for each cells. kinput2, erm, Input Method which supports the multiple Input Contexts basically can has different behaviors every Input Contexts. It's the applications choice.
Comment 3 Caolan McNamara 2005-07-28 15:28:07 UTC
seems good in 1.9.121-3 rawhide. caolanm->akira can you confirm this is now desired behaviour ?
Comment 4 Akira TAGOH 2005-07-29 04:47:42 UTC
Yes, it looks good. however sorry, this is an RHEL3 bug. reopening.
Comment 6 Caolan McNamara 2005-08-16 08:31:22 UTC
Adding to proposed list, though likely relatively large impact and somewhat risky IMO for 1.1.X codebase.
Comment 12 Caolan McNamara 2006-04-12 07:59:45 UTC
No issuetracker score, no IM updates planned. Decision has been made to move such IM bugs to RHEL-5 nextrelease (OOo 2.0.X series)