Extension checking is in the Mozilla backend and changed significatly between
2.40 and 2.46 (mostly not for the better). Signing requirements are turned off
but still some checks for sideloaded apps are done. Extensions might get
disabled but from tests reenabling them again worked. No reinstall needed.
And SeaMonkey is not Fx or I would probably looking for another browser :)
FRG
Desiree wrote:
On 12/27/2016 8:10 AM, Ken Rudolph wrote:
Frank-Rainer Grahl wrote:
Yep. I've been using Sea Monkey since Mozilla abandoned its predecessor the
Mozilla Suite and never had problems other than maybe a minor one occasionally
when upgrading. Upgrade to 2.46 was a disaster on my default profile but ok
on a newish profile with only two extensions. I can't understand why we were
not warned that no checking of extension compatibility with this version would
be done and that NO extensions being used that were converted via LemonJuice's
SeaMonkey extension converter would work and that disaster would ensue if we
tried to update without first uninstalling all converted extensions. I'm
left wondering why SeaMonkey is being continued since it is now Fx and no
point in it.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
