change of FirefoxHTML filetypeID in the Windows registry causing problems
I do a great deal of HTML editing and for that reason have developed a set of registry entries that use the FirefoxHTML file type ID in the Windows registry (HKLM\SOFTWARE\Classes\FirefoxHTML). However, after not upgrading FF for nearly a year, I just did so. Lo and behold, the file type ID has changed from plain--and reliable from update to update--FirefoxHTML to something new: FirefoxHTML-5440E01DFA42414. This kind of thing is a real PITA, plus I can't see any reason for it. Why did the developers made this move?
It would really suck if they were planning on giving this main registry entry a new number with every FF update. If they're going to do that, I'm going to have to completely restructure my approach to these registry entries so as to bypass the FF file type ID altogether. But I need to know. Does anyone have any relevant info?
Tutte le risposte (4)
I do not. Find that value and tomorrow sometime or later tonight there is a Firefox update to 56.0.1, see if the values change.
If stay same maybe the answer your looking for but the Big ver 57 update by next month ( I think, or after MS Update Fall Release) is a big change coming as per http://mashable.com/2017/09/27/firefox-quantum-beta-launch/?utm_cid=hp-r-1#CBLwglkKsqqU Or do another search for Firefox Quantum
Report back after tomorrows update as to what is going on. Thanks.
Nah, I'm working under a looming deadline and don't have time for experimentation. Besides, if this happened once, it can happen again, and I need to foolproof my solution against that as far as possible. Therefore I've now devised a registry solution that bypasses FF's filetypes altogether and only references FF for a single Shell\open direct to firefox.exe--and hopefully they at least won't change THAT.
But thanks for responding.
Hello,
I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution more easily. Thank you for contacting Mozilla Support.
Um, the problem did not get resolved. The question was not answered. I decided to work around it myself, but my decision did not take care of the underlying issue. So it would be misleading to other users to mark it as solved.