605273 - Sometimes IME composition string is inputted on floating window and cannot input to editor

Status: RESOLVED INCOMPLETE

Description

[Hyungsup Kim]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6) Gecko/20100101 Firefox/4.0b6
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

When I try to type Korean either the Korean keyboard is disabled, or there is a small white rectangle box at the bottom and only shows one syllable at a time. It's impossible to input any Korean character.

Reproducible: Always

Steps to Reproduce:
1.Turn on firefox
2.Try to type Korean in any text box or address bar, search bar so on...
Actual Results:  
As explained above

Expected Results:  
I should have been able to type Korean.

It's still a beta version and I remember coming across this bug back in the days when it was 1.5 (I think)

Comment 1

[Masayuki Nakano [:masayuki] (JST, +0900)(Away from Bugmail Dec 27-Jan 3))]

I don't understand this bug.

I can type Hangul characters by any Korean IME mode such as 2-Set Korean, 3-Set Korean, 390 Sebulshik, GonginCheong Romaja, HNC Romaja.

What IME do you use? And can you reproduce it with new profile? I need more details of STR.

Comment 2

[Masayuki Nakano [:masayuki] (JST, +0900)(Away from Bugmail Dec 27-Jan 3))]

Wow, I reproduced this bug with trunk on 10.5, but I'm not sure the STR for now.

Comment 3

[Gen Kanai [:gen]]

Channy, can you check with the Mac users in Korea about this bug?

Comment 4

[Channy Yun [:channy]]

Joone, would you check this bug together?

Comment 5

[Gen Kanai [:gen]]

If there is a larger group of Korean Mac users we could contact, that would be helpful too.

Comment 6

[Junho Choi]

Well. Today I upgrade to FF 3.6.11 to 4.0b6 (MacOS X SL).
No issue at all in Korean input. I followed the step to reproduce above but failed to reproduce.

One thing I'd like to note is I am not using default Korean IME.
I am using Baram IME (http://baramim.blogspot.com/) so maybe that's a difference.

Comment 7

[Channy Yun [:channy]]

I got several replies from twitter, but there is no Korean input problem in Fx4b6 on Mac OS. hmm... 

@Hyungsup Kim, would you attach screencast for your step in this bug?

Comment 8

[Hyeonseok Shin]

Works for me on Mac OS X 10.6.4 with 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6) Gecko/20100101 Firefox/4.0b6'

Comment 9

[Joone Hur]

Typing Hangul works well on my mac with the default Korean IME and Baram IME. (Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6) Gecko/20100101 Firefox/4.0b6)

Comment 10

[Gen Kanai [:gen]]

Another BARAM IDE user who has tested input in FF4b6 without problems.

http://twitter.com/#!/Taeyoung/status/28008150249

Comment 11

[Hyungsup Kim]

This happened to me when I have overwritten Firefox 4.0b6 over the latest stable firefox.
Now I have also installed namoroka from 3rd party supplier who tweaked it for intel snow leopard.
For some reason I don't have any problems with Firefox 4.0b6.
Hope you guys can try it.
I can't recreate the bug because installing the stable release has fixed it.

Comment 12

[Channy Yun [:channy]]

(In reply to comment #2)
> Wow, I reproduced this bug with trunk on 10.5, but I'm not sure the STR for
> now.

You mean nightly build or fx4b6 on 10.5?

Comment 13

[Masayuki Nakano [:masayuki] (JST, +0900)(Away from Bugmail Dec 27-Jan 3))]

Hi, thank you for your testing and comments.

I can reproduce same bug with Japanese IME with latest trunk on 10.5.

The STR is:

1. Launch Fx
2. Load http://bugzilla-attachments.mozilla.gr.jp/attachment.cgi?id=2974
3. Click search bar of Fx
4. Try to input a character via IME

Then, the inputted character will be on a floating window and cannot enter the composition string to Fx. But I *cannot* reproduce this bug on 10.6 with this STR. I'm not sure whether they are strictly same bug or not, however, this could be a good hint.

Steven, do you understand why the loading plug-ins causes this bug? When this bug is reproducing, native focus isn't strange, correct ChildView's processKeyDown is called and processKeyDown calls [super interpretKeyEvents:] correctly. However, that does NOT cause next step. I.e., any NSTextInput methods are not called after [super interpretKeyEvents:]. It seems that IME doesn't adopt to our NSTextInput protocol at that time. I have tried to understand what's happening, but I have not found the answer yet...

Comment 14

[Hyungsup Kim]

Yes this is the same bug I was talking about!
I was using fx4b6 on snow leopard.
If it helps, I'm not able to recreate this bug anymore after installing http://www.latko.org/media/namoroka-3.6.4.dmg


(In reply to comment #13)
> Hi, thank you for your testing and comments.
> 
> I can reproduce same bug with Japanese IME with latest trunk on 10.5.
> 
> The STR is:
> 
> 1. Launch Fx
> 2. Load http://bugzilla-attachments.mozilla.gr.jp/attachment.cgi?id=2974
> 3. Click search bar of Fx
> 4. Try to input a character via IME
> 
> Then, the inputted character will be on a floating window and cannot enter the
> composition string to Fx. But I *cannot* reproduce this bug on 10.6 with this
> STR. I'm not sure whether they are strictly same bug or not, however, this
> could be a good hint.
> 
> Steven, do you understand why the loading plug-ins causes this bug? When this
> bug is reproducing, native focus isn't strange, correct ChildView's
> processKeyDown is called and processKeyDown calls [super interpretKeyEvents:]
> correctly. However, that does NOT cause next step. I.e., any NSTextInput
> methods are not called after [super interpretKeyEvents:]. It seems that IME
> doesn't adopt to our NSTextInput protocol at that time. I have tried to
> understand what's happening, but I have not found the answer yet...

Comment 15

[Steven Michaud [:smichaud] (Retired)]

(In reply to comment #13)

Very interesting!  I'll bet this is a plugin focus issue, and will be
fixed by the patch I'm currently working on for bug 601182.

Flash 10.1r85 (the current version) supports IME using the floating
input window.  So its appearance is a sign that the Flash plugin still
thinks it has the keyboard focus (even though it really doesn't).  The
problem goes away (inline IME starts working) if you click on the
desktop (or another app) and then on the FF browser window's titlebar
(which presumably informs Flash that it no longer has the keyboard
focus).

I hope to post my patch for bug 601182 later today.  I'll also do a
tryserver build.  I'll comment here when it's ready.

Comment 16

[Steven Michaud [:smichaud] (Retired)]

No, my patch for bug 601182 doesn't fix this bug.  Sigh.

It's probably at least partly a plugin focus issue, but I suspect it's also a bug in the Flash plugin -- maybe a bug in its (presumed) workarounds for the broken way in which Firefox currently handles plugin focus.

Comment 17

[Steven Michaud [:smichaud] (Retired)]

Bug 587667 is probably also involved.  IME input currently doesn't work properly inside Flash plugins (using Flash 10.1r82 and 10.1r85) on the trunk.  This seems to be an issue with how the Flash plugin handles Cocoa-event-model text input.

Comment 18

[Masayuki Nakano [:masayuki] (JST, +0900)(Away from Bugmail Dec 27-Jan 3))]

I cannot reproduce this bug with Nightly on 10.11. Do you still reproduce this bug on your environment?

FYI: http://bugzilla-attachments.mozilla.gr.jp/attachment.cgi?id=2974 was moved to http://bugzilla.mozilla.gr.jp/attachment.cgi?id=2974