When at a root domain (like http://www.mozilla.org/) right clicking and saving the page, as either html-only or complete, saves the file with the extension *.htm I'm told this may be an interaction with the OS thing and that it was fixed at one point. I see lots of bugs about appending extensions to files with extensions already but none about this particular case.
Check that the registry key HKEY_CLASSES_ROOT\MIME\Database\Content Type\text/html has the key "Extension" with ".html" as value and not ".htm". Mozilla uses this value if it knows the MIME type but has no filename with an extension.
It would be nice to have an override in about:config instead of having to change this in the registry.
Indeed. But at least this way, the mess M$ made will be cleaned up for the benefit of other apps that may use it.
Thanks for the bug report. Relying on the OS for the default file extension here is a sane way to handle this case, and adding complexity here to allow .html to be used as the default extension isn't worth supporting.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
Adding complexity? I would think hard-coding the correct extension for the file type to be simpler than trying to get it from the OS.
Adding this as an about:config option would mean that it will only get used by a super-tiny set of users, and will make troubleshooting issues harder since another code path is followed. Since the feature wouldn't have a straightforward path for reach >20% of users, it isn't worth the extra code + support complexity.
Requiring users to go into the registry to fix this would exclude people on networks run by control freak businesses/institutions that block them from editing the registry. But even among those who do have access to it, how would the average user find out anyway that that's what they need to do? Moreover, you haven't commented on the suggestion of just hard-coding it. Another idea would be to program the installer to apply this correction to the registry.... For that matter, what's the situation with this on platforms other than Windows?
You need to log in before you can comment on or make changes to this bug.