Onno Ekker wrote:
Op 30-10-2019 om 00:08 schreef Frank-Rainer Grahl:
Hawker wrote:
FRG
Could you also elaborate a bit on what's realistic for extension
developers? My extension is compatible with Thunderbird 52, 60 and 68,
and also with SeaMonkey 2.49 and 2.53, but in order to be compatible
with multiple versions I detect the Gecko version and that will probably
fail for SeaMonkey 2.53 when it stays on Gecko 52 (or is it 60?) and it
backports functionality from TB/Gecko 60+.
2.49 is at the end of its life when the first 2.53.1 will be released. 2.53.1
already switched the gecko version to 60 because major websites are doing more
than stupid ua sniffing.
For 2.53.1 we backport but only the "good" stuff. There should be no breakage
if it already works. Things like ChromeUtils.Import have been backported. The
remaining 60 ChromeUtils enhancements are on the list. Just a matter of time.
2.57 is still way off. We are currently removing rdf support but to be usable
it needs webextension support. I don't have an ETA.
68+ (would be SeaMonkey 2.65) and deprecation of XUL extensions is currently
not being worked on. Frankly I can't tell you what happens after 2.57. We
could make SeaMonkey compatible but this would drop a lot of current
functionality. Currently 68 and up is broken.
Personally I don't care about anything beyond 2.57. Mozilla did a good job to
scare me off with the post 60 changes (and some of the 57 to 60 stupid ones
too like viewsource in a tab only).
Any enhancements for 2.53 go into the later releases too. When we are at 2.57
we need to decide about the future. Can only speak for myself but I wish I had
a firm plan.
In any case nothing to worry about in the, lets say, next 2-3 years. 2.53.1 is
working really well and I enjoy working on and with it very much. I think the
same is true for the other team members.
FRG
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
