369055 - Korean character is still remaining even changing the input method to English

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Bada]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

All international users are using 2 different language for input method.
After using Korean input, then changed to English. But Korean language is still remained in the input box. It won't be changed to english like following link.
Please look the following link (http://138.23.127.203/inputwrong.jpg) or allow this image to show. <img src="http://138.23.127.203/inputwrong.jpg">
Thanks

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Bada]

Attachment: input wrong

Comment 2

[JongAm Park]

I also noticed this problem, and it is very annoying.
Somehow, the Firefox doesn't seem to maintain input method status.
This usually happens when you switch among a few applications including the Firefox. What I mean is this :

- use the Firefox and type in some Korean text
- change to other application program like the Xcode or the TextEdit
- change back to the Firefox

The input method icon on the menubar indicates that it is in English mode, but it is not actually exactly like that.
If you type, the Korean characters are displayed without being composed.

Comment 3

[JongAm Park]

Can anyone guess whose fault is this? MacOS X's management with the input method, or Mozilla's?
I took a quick look at the mozilla source code, but I didn't find what method would be called when you start typing in the URL field. If there is a problem in the Mozilla side, it should show the problem there or if it is MacOS X side of a problem, some treatment with interaction with the MacOS X should be placed there.
 

Comment 4

[Bada]

It also happens on new released Netscape navigator. But I haven't got this problem with Camino browser. Try to use Camino. It makes you happier. 

Comment 5

[JongAm Park]

Well, Mr. Bada
It is for sure that the Netscape Navigator shows the same problem. It use the same codes. However the Camino uses the Cocoa or Carbon call, although the Gecko engine is the same. I am pretty sure that it is the reason why the Camino doesn't have the problem. ( However, the Camino has its own problem. )
Also, this is for figuring out the bug and fixing the bug.
So, using the Camino instead of the Firefox doesn't help to fix the bug in the Firefox source code.

Comment 6

[JongAm Park]

I tested with 2.0.0.5pre source code downloaded using the CVS on June, 18.
Although I debugged it, I couldn't iterate the same problem any more.
I have used it for 30 minutes.

Mr. Bada
Can you try the 2.0.0.5 pre version also? You can download using the CVS and build it, or you can download at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.8/firefox-2.0.0.5pre.en-US.mac.dmg

Probably the prebuilt nightly version can contain more recent modification which doesn't appear in the source code I obtained, because mine was built 1:05AM while the nightly version was built 8:03 AM.

Comment 7

[JongAm Park]

It still happens with 2.0.0.5pre version, although it is difficult to find the condition where this problem happens.

Comment 8

[Bada]

I already switched to Camino for this terrible reason. Camino is the right answer for Korean input method. 

Comment 9

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 1000 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.

Comment 10

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 11

[JongAm Park]

This is very old bug, and it doesn't happen anymore.
I'm sorry that I didn't update any comment. I'm not active in mozilla dev anymore, although I still use the Firefox. (The latest nightly, to be more specific. )

I will change the state of this bug.

Comment 12

[JongAm Park]

(In reply to comment #11)
> This is very old bug, and it doesn't happen anymore.
> I'm sorry that I didn't update any comment. I'm not active in mozilla dev
> anymore, although I still use the Firefox. (The latest nightly, to be more
> specific. )
> 
> I will change the state of this bug.

Oops! I'm not the person who reported this problem. Bada should change the state. I believe he was just a user. He just changed to Camino at that time because it worked for him. ( He didn't seem to be interested in Mozilla codes or help to improve the mozilla code. Whether he has a problem with one product or not, if he was interested in Mozilla, he should have interest in enhancing the codes! )