These are what constitutes SeaMonkey's value proposition you get a (barely) usable e-mail client and a barely usable IRC client built right into your web browser. The "applications" in the "Application Suite" aren't all that. It is alright, but there isn't really any compelling reason to use SeaMonkey over Chromium based browsers or, if you want the same rendering engine Firefox uses, plain Mozilla Firefox. working web browser based on the same rendering engine Mozilla Firefox uses. There is an address book for it that works alright. It has some shortcomings, but it works fine. The e-mail client is largely based on older versions of the Thunderbird e-mail client. There are a few odd bugs in the HTML editor that, if memory serves, were there in the late 1990s when what later became SeaMonkey was known as "Netscape Communicator". Today it's something those who lived through the 1990s can fondly look at as a reminder of those days it has no other practical purpose what so ever. The HTML page editor is something that would have looked neat and impressive in the early 1990s. That is specially noticeable in the non-browser parts of the SeaMonkey "application suite". SeaMonkey development has essentially stood still for decades. There are some nice gems among those that are available to be used in SeaMonkey, but not current Firefox versions, but it makes it very hard to switch from Chromium or Firefox to SeaMonkey if there are 5-10 extensions you are accustomed to using. This means that only older (outdated) no longer updated Firefox extensions can be used by SeaMonkey. SeaMonkey is unable to use these new extensions. Then Firefox went ahead and deprecated all the good extensions for that browser and required all new extensions to use a new API. It used to support the same extensions as Firefox. Support for, or lack thereof, web browser extensions is the biggest flaw in SeaMonkey's web browser functionality. SeaMonkey can render web pages as they should be rendered, and more advanced web pages relying on heavy JavaScript-use work fine. The rendering engine in modern 2.5x.x versions use the rendering engine from a recent Mozilla Firefox LTS release. The web browser part of SeaMonkey used to be used on its own thing. The non-browser parts have barely been maintained the last decade, they are nearly identical to what they were 20 years ago. The other "applications" in the SeaMonkey "application suite" are there and they can be used to read and write e-mail and chat on IRC. Thanks to all who made possible this release.SeaMonkey v2.53.7 with a web browser window and the built-in HTML editor, and the buit-in ChatZilla IRC client. And many of them are UNCONFIRMED or outdated (have been fixed in between). Possible new bugs, caused by regressions in Firefox oder in Thunderbird, which also might affect SeaMonkey.Ī horribly long list, what does not consider that not all Thunderbird– and Firefox-bugs are relevant for SeaMonkey.Possible new bugs in SeaMonkey - only those with Status New or Assigned already have been confirmed as real bugs.The “ Known -Issues“- list is outdated, here an attempt for a more realistic overview. Not all bugs in Firefox or Thunderbird do affect SeaMonkey, but also it is not sure that all fixes will work in SeaMonkey. Bugs which have been fixed in Thunderbird and Firefox since SeaMonkey 2.38.Bugs in SeaMonkey 2.38 what have been fixed for SeaMonkey 2.39.I do not know which Firefox42 – features made it into SeaMonkeyĪ Bugzilla query shows SeaMonkey 2.39-specific RFE-Fixes – for “ Bug 1153577 – Users should be able to hide the menu bar and show it with the ALT key” there might be a problem with Ubuntu/Unity. Lesson learnt? Green really isn’t green until one confirms that it’s green otherwise, it could be fuschia, red or purple.Īdditionally to the very outdated “official” Release Notes here you find some more information concerning changes with SeaMonkey 2.39. Apparently the system I’m using has no access to the new upload host. Windows, on the other hand, is problematic. Self-deprecating humor aside, I think I’ve fixed the Linux and OSX64 side. It’s contrary to what I believe, but what I think happened is that the ‘receiver’ of the uploads discarded them quietly. Then I realized that “it wasn’t lying and the uploads didn’t make it” isn’t a contradiction. (You have to be here to see my facial expression… complete confusion.) It wasn’t lying and the uploads didn’t make it. The log within that step said “upload complete”. Looking carefully at the download site, ‘lo and behold, none of the uploads to the servers are actually getting there.īut the tree was green! Even the step on the buildbot master said green. MC on #seamonkey pointed out that there hadn’t been any uploads to the server since. Long story short, SeaMonkey’s upload and download hosts have changed and with that, some of the configuration parameters needed changing in the backend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |