294510 - saved html file won't open from Explorer

Status: RESOLVED WORKSFORME

(Firefox :: File Handling, defect)

Description

[CEP]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

When saving a file as ".htm" (using File | save As), the file appears to save
correctly, and can be opened from inside of Firefox using the File | Open
dialog. However, even though Firefox (through 1.0.3) is set as the default HTML
file handler, navigating to the saved file using Windows Explorer, then
double-clicking the icon, results in a null operation.

Reproducible: Always

Steps to Reproduce:
1. Save http://www.fu.bar/index.htm as c:\My Documents\fubar.htm
2. Minimize or close Firefox
3. Open the folder c:\My Documents
4. Double-click on fubar.htm

Actual Results:  
Nothing

Expected Results:  
Opened to a tab displaying the saved fubar.htm

This inconsistently does the same thing with the File | save Page in archive
command, but I have not tested it stringently enough to determine a cause or
default (whether expected or not) behavior.

Comment 1

[Matthias Versen [:Matti]]

Please don't report bugs from old builds ("Firefox/1.0.1" is old)
Save as archive is no Firefox function, is from an extension.

This is wfm on win2k3 with FF1.0.4
Please reopen this bug ONLY if you get this with FF1.0.4 and WITHOUT extensions.
USe the safemode to disable all extensions for a test.
(http://kb.mozillazine.org/Safe_mode)

Comment 2

[CEP]

Matti, the particular machine from which I was posting only had 1.0.1 on it, but
I've confirmed that behavior for all versions later than 0.9 on other machines,
specifically including 1.0.4. That's also why I noted the "save as archive"
behavior separately: Although it's from an extension, so far as I can determine
it appears that there may be--not necessarily is--a relationship to the general
problem with file opening.

If, however, you're saying that your installation of 1.0.4 does not duplicate
either problem, please state so. I can't tell unambiguously from your message
what you really mean. I'm leaving this as "resolved" for the moment... but I
suggest that y'all assume that someone who goes to the trouble to report a
problem in detail from a machine using an older build just might have tested the
problem on more-recent builds, but is posting from a "non-primary" machine,
until you've specifically tried the same procedure.