From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2+) Gecko/20010724 BuildID: 2001072403 Double clicking on a file (html, gif, etc.) from the desktop/windows explorer fails to result in the displaying the file if Mozilla is already open. The file is shown if Mozilla is not yet open. This may be closely related to bug 59078 (http://bugzilla.mozilla.org/show_bug.cgi?id=59078), but this bug is more serious than bug 59078, since the file does not appear at all (in bug 59078, two windows appear and the file appears in one of them). Reproducible: Always Steps to Reproduce: 0. verify windows integration settings set to open html files: a. Exit mozilla. b. Find an html file on the local hard disk via windows explorer c. Double click on file. (File is displayed, though two windows appear as in bug 59078. This step verifies that Mozilla is set to open html files. If it doesn't work, probably need to change windows integration settings Preferences/Advanced/System) 1. Open a file from windows explorer a. (optional) Exit mozilla and Start Mozilla (verifies that it still happens in a fresh mozilla, so it is not some persistent hang. home page is blank.) b. Double click on an html file on local disk from windows explorer. Actual Results: A browser window opens. The file does NOT appear in the window. The URL does NOT appear in the URL field. Expected Results: A browser window opens. The file does appear in the window. The URL does appear in the URL field. Same results for gif, jpeg, etc. files.

Worksforme Platform: PC OS: Windows 98 Mozilla Build: 2001073003

I am having the exact same problem after installing 0.9.3 (Build ID: 2001080110) installer.exe version. Note: I can the same local page by: - right-clicking and chosing Open with > Mozilla - dragging the file into a Mozilla window - dragging the file onto a shortcut to mozilla.exe - typing "mozilla.exe somepage.htm" at the command prompt Platform: PC OS: Windows 2000 Pro Mozilla build: 2001080110

WFM, Win98SE, 2001080703

I tried the same build (2001080110 or 0.9.3) on a different Windows 2000 PC and it worked fine. Here's some additional info about the two Win2k installations I was using to test this and the way I performed the install. I hope some of this will be useful when testing this. Similarities: Platform: PC OS: Windows 2000, service pack 2 After installing 0.9.3-installer.exe: - When prompted by Mozilla I have answered "Yes" to enable windows integration. Differences: Test outcome: PC 1: bug confirmed PC 2: WFM Previously installed Mozilla version: PC 1: 0.9.2-talkback.zip PC 2: 0.9.3-talkback.zip (Please note that the installer.exe build was installed into a completely different folder than the zipfile builds I was using before) I will try to test on other Windows 2000 installations as well.

I've seen this before. Problem is due to the registry has one moz registered but a different one is running and under w2k for some reason the file is not opened. Might be DDE?

-> law

->097/p3

Resetting target milestone for all "window integration" bugs to mozilla0.9.8. I'm working on performance and won't get to that till next milestone.

Not getting to this, either.

Targeting for "future." Reports of some WFMs makes this one lower priority.

I get this with any local .html file, including email attachments in Outlook.

See my suggested solution in bug 59078.

Changing qa contact to me, as I am working on these now ;-)

qa contact windows integration-> pmac

Is this still a problem?

-> works for me (w2k, 1.7.6), and based on lack of activity in this bug from others. Problem was most likely a registry problem, and to reproduce it probably requires getting some version prior to 0.9.2 installed and then maybe upgrading to 0.9.2. I tried 0.9.1 and for a while 0.9.2 produced two windows of the mozilla home page (default home page) when I clicked on an html file in windows explorer. I ran 1.7.6 and clicked ok to make windows setting match integration preferences, then went back to 0.9.2 it no longer showed the home page. So it looks like 1.7.6 is doing something to fix that old registry problem.