xeonx wrote:yuoo2k, Yes, it is unfortunate that Firefox is pushing to completely remove XUL support, instead of just discouraging it, as there are a few extensions that can't or won't be ported to it.
I think I can speak for the community in saying: thank you so much for all your hard work in creating this, and the many hours of time and frustration you have saved everyone by doing so!!
Will you please consider at least an attempt to port to WebExtensions if it all possible, as this is one of the critical extensions that makes Firefox worth using over Chrome.
Also, can you release this source code this on GitHub and update the addon page with warning about the future, link to source on GitHub, and request for volunteers to help port it?
Ditto on the thanks to yuoo2k. I would certainly understand if he ends up walking away from it. The last few years of Mozilla changes have made it tough for add-on developers to keep pace.
Note that the
ABH2 page has a donation link, and yuoo2k may not have rec'd much or any such incentives. I'd be willing to donate if I thought it would help, but I'm only one person, so my sole contribution is not going to be enough.
As far as porting ABH2 to WebExtensions (WExt) goes, keep in mind that it will first depend on what the WExt API's allow. As we're hearing, some add-ons will go dormant soon because said API's
appear to be more restrictive and don't (yet?) offer the necessary comparable functions/etc.
In my case, I plan on switching from FF 55.x Release to FF 52.x ESR - for as long as it lasts - while I see how many of the add-ons I use get ported.
And then depending on what happens, I may end up switching to - or using in tandem - some FF fork like SeaMonkey, Waterfox, or Pale Moon. The latter two have pledged continued support for XUL/etc for the forseeable future (see
WF1,
PM1,
PM2.) And in the case of PM, they've had a
compatible version of ABH2 +
GitHub page for some time now.
In the meantime, I'd be willing to pitch in on fixing/maintaining the current ABH2 code for one of the forks, and to possibly help port it to WExt down the road - should that be possible.