Rated 3 out of 5 stars

by Salopsnail on Aug. 20, 2017 ·

Those blaming codefisher for the incompatibility are out of order, when Mozilla moves the goalposts then evry one looses out, making these new rules (i.e. that the new way of doing things ( WebExtenions) rules out a lot of the posibilities for addon devolopers) For Michael the fact that only a maximum of 1 button per extension means that in it's present form this addon is as dead as a dodo. This is a crying shame as a diabled user it has made a big difference to my productivity for which there is very little chance of a sensible replacement. Mozilla wants just 1 button per extension so I will need abaout 35 addons to comply with this rule and that is not including the other addons that I use.
So please stop giving the blameless third party app developers a hard time and pettition Mozilla instead to be more flexible with the rules.
ONE SIZE FITS ALL DOES NOT WORK !!

by Michael B. (Developer) on Aug. 21, 2017 ·

Yes certainly dead as a dodo. I just put up a notice to that effect. However I do hope to put together many of those 35 add-ons you need. I finished off a few today.
People are partly right to blame me. I did drop the project for awhile due to other commitments, I could have acted sooner if I had the time to resolve this.
I understand what they are doing and why though. It does make add-on malware very hard, which is good. And it will prevent rogue add-ons slowing down Firefox. They are also looking to create a stable API that they can promise will always work (I greatly approve of this). It is quite painful though to make the transition, as many things have to be rethought and rewritten. The API is also limited so that many things we were used to doing will no longer be possible. I am hoping that can change with time.