Because there is no link to provide. You have to go over these lengthy status meetings. There is no summary for the one lazy to read. Finally you read some of it. But what you read is too few to know what's really happening. The guy you mention is one of two main developers of SeaMonkey, this post of him on MozillaZine I did read. It shows he is confused by manifest v3 and doesn't know what to do next. Simply as that. This means SeaMonkey is unable to have WebExtensions support because there are too much works, but SeaMonkey is also unable to retain old XUL addons because the needed apis are all removed by Mozilla. BTW, SeaMonkey 2.57 (comm-esr60) could be never a thing but the version number being retained for future use (read the status meetings again, no link to sum it all for you). All of the development currently on SeaMonkey 2.53 (comm-esr56).jobbautista9 wrote: ↑2022-06-20, 15:02You keep saying that, yet you haven't provided any link to one of their status meetings where they said that.
Now I ask you who will change the addons to adapt to the new apis since the old apis were removed as he said? The fact is the whole XUL platform being removed and not simply some apis. Nothing of XUL was left. You liked to argue so much but too lazy to do a simple test to verify it. It seems you are not actually running any versions of SeaMonkey, too. What you do is just talk and argue. I repeated it again: download SeaMonkey 2.57 dev from wg9s and try installing some old XUL addons. You will see they are installed without any problems but they simply not work. This is enough to prove it?
Just because they used to said SeaMonkey 2.57 will still keep XUL based addons doesn't mean they will or can do that. The fact is they changed their statements very regular. They can't keep what they talk because the reality is so different than ideology. The reality is so harsh. You got it?
BTW, Finally I have given up on SeaMonkey. Some websites that crucial to me no longer work correctly. The cause is not because they use any new fancy Chromish technology but because the tracking protection of SeaMonkey. They work on Pale Moon without any problems. I tried my best to disable or at least configure tracking protection on SeaMonkey either via the Preferences graphical interface or about:config but there is simply no way to do so. SeaMonkey really has all of the backend code they got from Mozilla codebase, but the frontend to configure and manage thing is simply not there. Don't talk with me about SeaMonkey anymore I will not answer.