Add-on “Go Parent Folder” stopped working

As already mentioned in Unofficial SeaMonkey 2.53 by user wg9s and Test Results for Add-Ons from ca-archive, “Go Parent Folder” (and also “Show Parent Folder”) don’t work any longer with latest 2.53 by user wg9s

• “Go Parent Folder” context menu appearing after rightclick on a bookmarks entry does no longer show  the Item “Go Parent Folder”, Problem is visible in Bookmarks Manager and in Sidebar Bookmarks Panel.
• “Show Parent Folder”: Table column can no longer be added in Bookmars Manager.

Screenshot from Build 20170731233559

Go Parent Folder and Show Parent Folder both worked in Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53a1 Build 20170731233559. That was a version with the little column selector in the most right table heading in Bookmarks Manager.

The first version still available on my PC where both addons do no longer work is Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53 Build 20180902143701. And in this version also the little column selector in the most right table heading has gone. That proves nothing, but might indicate the reason why the addons do no lnger work.

SeaMonkey 2.49.2 (ESR) – additional Release Notes

Blogpost Version 2018-02-16 (new)

We have a new release: SeaMonkey 2.49.2 (ESR)

Additionally to the official Release Notes here you find some more information concerning changes with SeaMonkey 2.49.2

You need a Bugzilla-Account for the queries here in the blogpost. All queries without any liability, because (not only) correct use of TARGET MILESTONE is controversial.

Mistakes in official Release Notes

I don’t know.

New features

SeaMonkey 2.49.1 (ESR) – additional Release Notes

Blogpost Version 2017-11-08 (Sprachpaket-Version)

We have a new release: SeaMonkey 2.49.1 (ESR)

Additionally to the official Release Notes here you find some more information concerning changes with SeaMonkey 2.49.

You need a Bugzilla-Account for the queries here in the blogpost. All queries without any liability, because (not only) correct use of TARGET MILESTONE is controversial.

Mistakes in official Release Notes

I don’t know.

New features

Add-On “PrefBar” crashes SeaMonkey 2.52 ⚠️️

One of my favorite add-ons crashes latest SeaMonkey Trunk-Builds like

UNofficial (by FRG) en-US SeaMonkey 2.52a1 (NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 Build 20170513191754 (Default Classic Theme) on German WIN7 64bit

When I launch SeaMonkey it crashes immediately if PrefBar add-on is active.

The problem is not Win64; x64 related.

Bugs:

• Bug 1364078 – CRASH when launch with add-on PrefBar enabled
• mozillazine Bug 26367 – SM 2.52 latest Trunk Builds CRASH when launched with Premier enabled

Can someone confirm the problem❔

Any theory concerning the roots of the problem❔

SeaMonkey 2.46 Release – additional Release Notes

Blogpost Version 2016-12-31

We have a new release: SeaMonkey 2.46

Additionally to the rather outdated “official” Release Notes here you find some more information concerning changes with SeaMonkey 2.46.

You need a Bugzilla-Account for the queries here in the blogpost. All queries without any liability

Mistakes in official Release Notes

• “The cursor may change … (bug 736811)” is WORKSFORME since 2014-11-27 (User NoOp told so on mozilla.dev.apps.seamonkey)
  I submitted  Bug 1325744 – 2.46 Release Notes “known issues” wrongly refers to bug 736811
  

New features

My UNCONFIRMED Bug Reports

I still report new bugs I find with status UNCONFIRMED, even if (after careful investigation) I am pretty sure that the report is concerning a real bug and complete enough so that a developer can take on. Reason is that I believe in the two-man rule. Often a review by an other user adds information, may be concerning additionally affected Operating System or an aspect of the problem not yet mentioned or something else. But in the SeaMonkey project, due to very limit “human QA resources” and the lack of interest of most SeaMonkey users to contribute to the project, the bug review process  is horrible slow, even Bug reports what can be reproduced easily do not find a user who is willing to do a test whether he can reproduce the problem.

SeaMonkey needs you

So in future I myself will change bug status to NEW after 2 weeks (or so) of waiting if I think that all requirements for starting bug fixing process are fulfilled and nobody confirmed the bug. But, of course, it would be great if YOUR help would make superfluous this proceeding with my own “confirmation”. Be courageous and grasp the nettle of confirming some [easyconfirm] bugs.

SeaMonkey 2.40 additional Release Notes

We have a new release: SeaMonkey 2.40

Additionally to the rather outdated “official” Release Notes here you find some more information concerning changes with SeaMonkey 2.40.

New features