Post-release post…


SeaMonkey is currently as far behind the release schedule (rapid release or otherwise).  Mozilla isn’t making it easier for us to release things; but, hopefully we’ll be under our own release schedule (if we’re not already) for Mozilla to have any affect on us.

That said, I can’t help but feel that I’ve dropped the proverbial ball  on this release.    I’d like to personally offer my own apologies for the delay.  It’s entirely and wholy my fault and not the fault of the other devs.   I have a lot of ideas to get things working again; but, I’m hoping I’ll get the chance to do what I’ve set out to do for SeaMonkey.

Yours truly,


14 Responses to Post-release post…

  1. Jean-Charles TEYSSIER

    Thank you for your work. DO NOT worry about delays 🙂


  2. I hope things will work out as you have purposed soon. I love SeaMonkey and it is literally the only Internet suite that’s left out there. Somehow I feel SeaMonkey is more RAM-efficient than Firefox. Thank you for all your effort and for keeping SeaMonkey alive.

  3. Thank you for this, your efforts are very much appreciated.

  4. hopefully a 2.53 release of Seamonkey will come before year 2019 ends

  5. Do not apologize! You are doing great work.

  6. Oh yeah!! Great Job Seamonkey Team. Thanks for all

  7. Be proud of yourself, you and the team have done a great job to get SeaMonkey back on track! Much obliged!

  8. Thanks ewong,
    It is all our passion to stay with our beloved browser, so we will continue!

  9. Thank you for keeping our beloved SeaMonkey alive!

  10. For the next release you should change the user agent to Firefox 60 ESR. Because Firefox is now at version 69 and version 52 is End Of Life websites have begun to flag Seamonkey as an “out of date” web browser. One example is github. To get rid of it, one has to go to about:config, accept the warning and create a new string, call the new string “general.useragent.override” (without quotes) and put the current Firefox ESR user-agent as the new value.

    The user-agent for Firefox 60 ESR is:
    Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

    Even the current Firefox ESR is getting quite old, so if the new ESR is out, use the UA for that version.

    This is the only problem right now, and it’s impacting the UX of the browser.

    Other than that, I’ve been using Seamonkey for a number of years now. Hopefully you’ll get all the quirks and problems you’re having solved soon!

  11. Is there anything really new in newer versions of Gecko and Firefox? By “new” I mean implementation of new elements of HTML, and not the obvious “bigger and slower”.
    If there isn’t, then I, as a user, don’t see any reason to follow them. Just backport the fixes and use fake user agent string, where needed.

  12. 2.53 already uses 60 because of github and other bad websites. Usually they work even with 52 functionality and a ua agent override but not always.

    > Is there anything really new in newer versions of Gecko and Firefox? By “new” I mean implementation of new elements of HTML, and not the obvious “bigger and slower”.

    Yes. JS modules, service workers, wasm, new css support and a bunch of other stuff. Some is already working in or has been backported to 2.53 but a genuine 2.57 release based on esr60 would be preferable.

    For a test drive try:

    Back up your profile. There is no going back to 2.49 afterwards without problems. An official release will support upgrading from the unofficial 2.53 because that is what the devs run right now 🙂

  13. Just want to leave a thanks to the devs. My suite. 🙂

    I can imagine some frustration and pain for the team but you did it. Well done!

  14. Good things come to those who wait. 😉
    I have faith that we’ll see 2.53 released before the end of 2019. 🙂
    KUDOS to All at the SeaMonkey council to keep our beloved browser going! 😀

Leave a Reply

Your email address will not be published. Required fields are marked *