Closed Bug 305040 Opened 19 years ago Closed 19 years ago

FirefoxHTML Windows file type lacks a type name

Categories

(Firefox :: Installer, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 270108

People

(Reporter: public, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

In order for File > New to work in Windows, the file types in question need to
have names. The Firefox HTML file type 'FirefoxHTML' has no name, leaving
Windows to refer to .htm and .html files as "HTM document" and "HTML document"
respectively.

This unfortunately stops File > New working for .htm and .html until you first
name the file type.

Reproducible: Always

Steps to Reproduce:
1. Install Firefox
Actual Results:  
The file type FirefoxHTML has no name.

Expected Results:  
The file type FirefoxHTML should have a name.
Related to/duplicate of bug 270108?
Actually, yes, the cause is the same, although the end result is different. I
imagine Windows fixed the issue in Windows 2000 (and Win Me?), such that unnamed
file types can still be manipulated. You cannot perform File > New on such types
yet though, in 2000 or XP.

I think the confusion for me surrounds the fact that I must have named the type
myself at some stage (hence mine being "HTML document" -- no capital 'D' for
"document" (I'm not American)), long before realising that it had to be done for
File > New to work. I mis-assumed that the type name had always been there, and
I was puzzled as to why it now wasn't on later installs on other machines :P

Marking as duplicate.

*** This bug has been marked as a duplicate of 270108 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
*** Bug 259376 has been marked as a duplicate of this bug. ***
*** Bug 260807 has been marked as a duplicate of this bug. ***
*** Bug 258816 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.