An active window is either the frame or dialog that has the focus owner or the first frame / dialog that owns the focused window. So deriving from this, a non-focusable frame can not become an active window. This is honored when a non-focusable frame is first shown on the screen. But when I maximize the frame and restore it, it automatically becomes active which is incorrect. Because it is still non-focusable. DKFM.getActiveWindow() returns the frame instance after it is maximized.

This is reproducible on 1.4.2, tiger and mustang on WinXP. Not reprodcuible on solaris/linux with XToolkit as well as Motif. On Solaris, the frame is always non-active.

I have attached a sample test. Execute the sample test. You would see a frame with a grayed out title bar. Check the console. A null would have been printed (refers to active window). Now maximize the frame. Click on the button. If the frame instance is printed on the console and title bar becomes blue, the bug is reproduced.
###@###.### 10/20/04 07:21 GMT

This is reproducible by clicking a choice on a non-focusable frame. As soon as the choice's drop-down is shown and hidden, the non-focusable frame becomes active.