Fulvio you have a talent for testing
I wouldn't have expected 1.02 to trash your older user profile if you told it to use a new profile. Are you certain you never let it at your 1.01 profile? 'Cause stepping into other random profiles and raising cain would be a bad bug.
Fulvio wrote:I started getting all sort of requests to make [1.0.2] default.
It's keying off the full path to the executable. So if you have the program in a different directory than the one containing your default browser (of course you do!) then it'll whine about not being the default every time you run it. But it should happen just once, immediately after each launch, and you should be able to make it stop by unchecking the "ask me every time" checkbox, or by setting the [tt]browser.shell.checkDefaultBrowser[/tt] pref in your test profile to [tt]false[/tt].
Fulvio wrote: I think that firefox will have a problem catching on, if even maintenance updates can cause such havoc.
I too think this is a terrible weakness in Mozilla products. Extensions, twitchy things inserted into the application after it's built and tested, written by a constellation of developers only distantly attached to the core development effort, I mean that's just begging for trouble. An extended Firefox is going to stumble when you start swapping out parts like a Borg drone.
Yeah, like you're not a geek, too.
Remember when updating your Windows OS was strictly for emergencies, something as likely to trash your computer as make it better? Gotta say, whatever you think of Microsoft they've poured a lot of effort into making their update story accessible to the bumblingest of fools, and their products are much much better for it. The thing about open source development, most work is done by volunteers, and installers aren't sexy.
I agree, Mozilla's update process appears to be very fragile, and it's a problem.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050313 Firefox/1.0+