Re: loading xul.dll success

Dave Yeo schrieb:
> Downgrading the browser isn't really supported by Mozilla, usually works
> but not always as they don't care or test.
But it's the only workaround to enable native text encodings for reading 
mail and news to some degree.
> Really if you need something to load URL's that don;t load with old
> versions, the newer the better.
Only in the area of HTML5. FTP still suffers from long standing bugs. 
Latest OS/2 builds are only useable under a Russian OS/2 system.
> Yes, if you disable an add-on with 31, it'll be disabled in all versions
> and everytime you load the newer version, it'll do the add-ons check.
> There's probably a preference to disable checking compatibility, but I
> can't find it looking quickly.
For the average user it can be annoying by using localisation add-ons. 
Customised builds with an applied set of add-ons can avoid some of the 
limitations of user-profile hosted extensions.
> You could use different profiles for 10 and 31. You'd need program
> objects for both with the -p parameter pointing at the correct profile
> along with -no-remote if you want to run both at once and of course,
> isolating the LIBPATHS
That's also a matter of timing. Even with separate profiles for 
different Mozilla application versions and the recommended settings 
libc/libcx can cause stack corruption and memory leaks resulting in 
"XPCOM cannot..." message box. Unfortunately only a reboot can heal in 
this situation.

--
Andreas