When an InputMethodWindow is created with which setFocusableWindow(false) is called, an extra focusLost event is delivered to the main frame window and the focus itself goes nowhere. To reproduce, compile and run the attached test case and then:

1) Press TAB key some times, then you can see that the focus is at either of those buttons in main frame window.
2) Click on the button named "IMWindow w/o calling setFocusableWindow(false)", then an InputMethodWindow appears.
3) Press TAB key some times, then you can still see that the focus is at either of those buttons.
4) Click on the button named "IMWindow w/ calling setFocusableWindow(false)", then another InputMethodWindow appears. This window is set to un-focusable state.
4) Press TAB key some times, but you will notice that the focus is gone somewhere outside of the main frame window.

Expected result: Even if the InputMethodWindow is set to un-focusable, creating that window should not affect the focus on the main window. This is preventing us from adding setFocusableWindow(false) call in InputMethodWindow.

naoto.sato@Eng 2000-12-13