136777 - The entered characters disappeared when using Korean IME in Composer

Status: NEW

Description

[Rui Xu]

This bug is separated from bug 128562, and need more fix. 
The original report is from Yoon Kyung Koo as follows:

-------------------------
I tested again with 2002-04-09-10-trunk mozilla-win32-talkback.zip.
Still the new bug works.
My test environment is Korean Windows 2k sp2, Pentium III 750MHz, 192MB RAM.
And actually the IME is default IME(2bulsik) and half width input mode.

Steps.
1. start mozilla
2. click on composer icon in the status bar.
3. then now it should be focused in a blank composer window and the Korean IME
will be in English input mode.
4. type in 'a'
5. type in a space.
6. then press the Korean/English conversion key.
7. type in 'ka' a Korean character and a space 
then the Korean character and the space will disappear.
I suppose it occurs only the first time Korean characters are entered.

the input sequence is
'a(some English characters)'<space>'KA(any one Korean char)'<space>
then the result would be
'a'

------- Additional Comment -------
For those who don't understand Korean I'll make the steps clearer.
I meant 'KA' or 'ka' to represent a Korean character (which pronounces 'ka').
I'm sorry to confuse you. If you press 'k''a' keys in sequence, those makes two
Korean characters not one.
To key in that Korean character I've intended, you should press 'r''k' in 
sequence.
Any one Korean character will make that bug happen, so you need to just press
the 'r' key in Korean input mode.

Comment 1

[Rui Xu]

cc -> [e-mail], [e-mail]

Comment 2

[Joe Francis]

I have a win NT box.  Will it hapen there?  If so, if I could get some help on
setting up the right environment to reproduce the bug, then I will be happy to
help investigate.

Comment 3

[Rui Xu]

Yes, I just confirmed it is reproducible on US NT4 + Korean IME. I will go to 
your cube.

Comment 4

[Rui Xu]

Updates:
Double checked with 20020422 branch build, with the same repro steps in original 
report, after step 7, the Korean character is still displayed, but the space 
disappears.

Comment 5

[Roy Yokoyama]

assigning to joe.
Please let me know if you need my help.

Comment 6

[Syd Logan]

Roy, it sounds IME-specific. I'm assigning back to you, if this is not correct
(and maybe that is the case, since you assigned to Joe), please reassign as
appropriate.

Does this problem happen just in composer, or dies it also happen in text fields?

Comment 7

[Syd Logan]

--> yokoyama

Comment 8

[Joe Francis]

grabbing this back.  I'm working on it, believe it or not.  It's just taking a
long time to investigate.

Comment 9

[Joe Francis]

nominating nsbeta1.  disapearing text is pretty evil.

Comment 10

[Frank Tang]

yokoyama, could you please take a look at this one?
rui- does this happened on url bar?

Comment 11

[Rui Xu]

>> rui- does this happened on url bar?
No, it doesn't happen on url bar.

Comment 12

[Frank Tang]

so the worst case is the one space got deleted. since korean currently is not
our target shipping place, nsbeta1- it. 

Comment 13

[Roy Yokoyama]

moving milestone

Comment 14

[Joe Francis]

adding myself to the cc list since i keep getting this bug taken away from me.  :-)

My current theory is that we are getting a bad composition string from IME in
this scenario.  But that is preliminary. 

Comment 15

[SeungYong Kwon]

Mozilla for Linux build 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126

still has this problem. But very hard to reproduce this bug and it
occurs time to time. ;-<

Comment 16

[Frank Tang]

I think both roy and me are off mozilla for more than 2 years. If these bugs are
still here now, I think the real stauts is 'won't fix'. If you want to reopen
it, please find a new owner for it first. 

Comment 17

[Travis Chase]

Mass Reassign Please excuse the spam

Comment 18

[Travis Chase]

Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all
the spam is his fault feel free to tar and feather him

Comment 19

[Travis Chase]

Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam

Comment 20

[Masayuki Nakano [:masayuki] (JST, +0900)]

Does somebody still have this problem? WFM?