From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20001019 BuildID: 2000101904 If the "Open Location..." dialog is active and a browser window steals its focus (such as when it finishes rendering a page), the dialog stays open and in front of other windows, but it cannot be made to focus again. This means that not only can it not be dismissed, but none of the Mozilla windows behind it will work. The only way out of this is to kill Mozilla with the task manager. Reproducible: Always Steps to Reproduce: 1) Launch Mozilla. 2) Click on any URL or type in any location. 3) Before the page finishes rendering, hit Ctrl-L or use the menu command "File:Open Web Location..." 4) Wait until the page behind the dialog finishes rendering. 5) Attempt to dismiss the dialog (or type in any text), or to use any open Mozilla windows. Actual Results: The browser window in the background steals focus from the dialog. The dialog, while it stays in front of other Mozilla windows, cannot be refocused (and therefore cannot be dismissed), and it continues to block access to the Mozilla windows behind it. The only remedy is to kill Mozilla and restart it (much like a hang, although this is not technically an actual hang). Expected Results: Either the dialog's focus is never stolen by the underlying browser window, or the dialog can be refocused by clicking on it, such that it works as normal.
Build 2000101908 win32. When the page is done loading, the dialog loses focus. Clicking on it once does nothing. The second click gets the focus on the dialog. Clicking on the background window also works. I'm not seeing any lock in the process, I don't have to kill the program. Fabian.
what theme are you using? modern or classic?
When I'd first reported this I had only tried it with Modern, but Classic is affected as well. The recent XPInstall problems keep me from trying it with any third-party skins.
over to XPApps
jrgm, isn't this a dup of that dialog modality bug 25684? or another toolkit issue?
This worksforme, today's branch builds, modern or classic win2k.
wfm in new win2k build...
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)