From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5 Description of problem: XIM server could be deactivated even if there is the strings in the preedit buffer. but IIIMF can't. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.input something but don't commit it 2.press ctrl+space 3. Actual Results: ctrl+space seems to be ignored Expected Results: IM is deactivated Additional info:
I consider this to be similar to Bug #136367 in purpose, however not a duplicate.
Oops... I mean Bug #135039.
Technically, it's a different bug. Bug#135039 is caused due to Escape key isn't assigned as the hotkey to close. however this isn't related the hotkey, since you can deactivate IM if the strings isn't in the preedit buffer.
I should look at #135039 first ;) I meant for Bug#136628. for Bug#135039, since all of keyevent passes through cannaserver on Canna LE to process the key events. and Escape key wasn't just assigned a facility to close. FYI :)
Version-Release number of selected component (if applicable): im-sdk-12.1-2
Are all LEs have this problem right now?
Not all LE are affected by this problem, but each LEs behave differently. chinput: accepts ctrl-space by switching off but pre-edit buffer is not clear so next when it is switch on anything that was entered before will be displayed. bug 132612 xcin and CannaLE: does not accept ctrl-space hangul does not toggle off the LE but it commit the char and move to the next position.
Moving component to CannaLE, will file another bug for xcin LE. Thanks.
Huh? the conversion on/off is notified by SC_TRIGGER_ON_NOTIFY/SC_TRIGGER_OFF_NOTIFY. I'm saying it's not delivered if the preedit buffer has something. instead, the hotkey such as ctrl+space is sent as the usual key event. we could fix this on LEs. but IMHO it doesn't make sense. what the component should be fixed is iiimsf.
*** Bug 137016 has been marked as a duplicate of this bug. ***
should be fixed in 12.1-5.
Confirmed fixed in 12.1-5