User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 If the JavaScript Console is the window which last had application focus in Mozilla, clicking on HTML links elsewhere in the OS (such as from an email application, for example) causes Mozilla to want to display the URL in the Console. Nothing happens. Expected behavior would be to instead focus and make use of the last-focused *browser* window, not just the last-focused window. Reproducible: Always Steps to Reproduce: 1. Open a browser window and go to any URL. 2. Open the JavaScript console. Make sure it is the focused application window before proceeding. 3. Go to an email application. (I used Microsoft Outlook 2003.) 4. Click on a link which was sent to you in HTML mail. 5. Expect to be taken back to Mozilla, in a browser window. 6. Notice that Mozilla has instead refocused the JavaScript Console, and no URL navigation occurred. Actual Results: Mozilla refocused the JavaScript Console, and no URL navigation occurred. Expected Results: The last-used browser window should have regained focus and navigated to the URL passed in from the OS.

I can't reproduce this bug on my system with any of Mozilla 1.7.3, Mozilla 1.8a4, or Firefox nearly-1.0. But then again all sorts of ugly system things are going on as I switch back and forth between different default browsers. That Firefox DDE bug 246078 seems to be coming and going as I do this, and there's the advanced.system.supportDDEExec issue with Mozilla... Sometimes in Mozilla the URL loads into a new browser window, sometimes the first browser. Sometimes other browsers launch temporarily and sometimes I get system error alerts. But always the URL loads into a browser window. Note according to bug 262978, the very same steps-to-reproduce do correctly open the URL in a Firefox browser window (in that case the bug is that the browser window isn't activated in place of the JavaScript console window). The salient difference between Mozilla 1.7.3 and Firefox Aviary is bug 246078 and bug 172962. Between them hardly any external URL handling stone was left undisturbed.

My original bug description was a little erroneous. I need to amend the details as follows: 1. The external URL *does* get loaded into an open browser window, but if the JavaScript console was the last focused window, it's possible not to notice that the URL has loaded, because the browser window doesn't regain focus. So it's more of a focus bug than a non-loading bug. 2. This behavior also happens if the Download Manager window was the last focused window in the application.

Ah. This is the Mozilla Suite version of Firefox bug 262978, then. Marking dependent. This bug(s) is probably just caused by Windows activating the most recent window in the target application when it sends the DDE event to open the URL (see bug 255123). Mozilla should probably activate the appropriate browser window itself under these circumstances, subject to adjustments described in those two bugs. I can't confirm this now because I'm rather geared up for Firefox but I'd be surprised if it were not a real issue.

WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050509 I have not idea if this is regression. But it happens with ALL the tools windows (downloads, extentions, etc), not just javascript console, and probably other pop-ups. So it's probably not a console bug. dup of 255123 or some other bug? Can anyone else confirm WFM?

(In reply to comment #4) > WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050509 > > dup of 255123 or some other bug? Can anyone else confirm WFM? clarification - WFM in the sense that I CONFIRM the bug is happening for me. (there are so many other focus bugs) is it a dup?

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.