Steps to reproduce: 1. run mozilla.exe -turbo 2. run mozilla.exe Result: a window appears but is not given focus. 3. Close the window. 4. run mozilla.exe Result: a window appears very quickly but is not given focus. 053020 Win98

Another one fixed by the changes described under bug 81712.

Might be fixed by patch for bug 81712. If not, then this isn't likely a -turbo problem. That is, you'd likely see the same thing regardless of whether Mozilla had been started with -turbo. The problem is that a second instance of Mozilla sends a message to the first. The first process then opens a new window and attempts to bring it to the foreground. But recent versions of Windows don't let other processes yank foreground from the application the user is interacting with. The bottom line is that the cmd-line session you're typing "mozilla" in has foreground and Mozilla (which doesn't), can't take that away. Technically, we don't really do SetForegroundWindow. If we did, then the newly opened window would at least be highlighted in the Windows task bar. Paul, can you verify whether this problem has gone away, or if not, whether it exists *only* if you start Mozilla with -turbo? Thanks.

Verified in Windows build 2001062703