Masaru Yokoi Reporter
	Description • 21 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4) Gecko/20030722
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.4) Gecko/20030722

If 2 or more input context are exist in one window, there are not separated.
When input some preediting characters into a text field without commit, and
click another text field, and input the key sequence to commit of XIM, the
strings are commited into the text field which input another text field as
preedit before.

I think this behavior is not good.

Reproducible: Always

Steps to Reproduce:
1. Build Mozilla-1.4 with Gtk-2.2.3 and USE_XIM defination.
2. Execute above mozilla with XIM. (e.g. with Kinput2)
3. Open a page which has text input field.
   e.g.: http://www.google.co.jp/
4. Click text input field of page, start conversion of XIM, input some preedit
text. and don't commit it. (e.g. input "aiueo" in Japanese and don't input
"enter" key).
5. Click the location text input field of mozilla. The status of input method
will be activated (conversion on).
6. Input commit key sequence of IM (like "enter" key), the preedit strings which
we input into the text field in the page before were commited into location text
field.

Actual Results:  
The strings which we input into another text field were commited.

Expected Results:  
I think mozilla should have input context for each input text field.

	Christian :Biesinger (don't email me, ping me on IRC)
	Comment 1 • 21 years ago

-> gfx:gtk I guess

	Christopher Blizzard (:blizzard)
	Comment 2 • 21 years ago

This isn't exactly easy to fix.  Right now we have one big multicontext. 
Because it's used for typeaheadfind.

I would much rather have more than one multicontext, myself.

	Masaki Katakai Assignee
	Comment 3 • 21 years ago

Taking.

Hanaki-san is now working on this issue.

For GTK1.2 widget, we used nsIKBStateControl:ResetInputState() to reset the
input state when input field is changed while pre-editing. We can do the
same thing in GTK2.

Hanaki-san, please attach your patch if code is ready for review.

To have multiple input context per each input field can be another solution.

	Shinichi Hanaki
	Comment 4 • 21 years ago

Currently, I have no idea how to fix this problem, cannot find out how
to reset input status when input focus is changed.
Need someone's help.

	Mats Palmgren (inactive)
	Comment 5 • 17 years ago

Does this bug still occur in a recent trunk build?

	Masayuki Nakano [:masayuki] (he/him)(JST, +0900)
	Comment 6 • 17 years ago

this should be fixed by bug 321468 (and bug 357568).

-> FIXED