Will Basilisk support fully WebExtension support?

[dark_moon]

..so addons like uMatrix work?: https://github.com/gorhill/uMatrix/releases/tag/1.1.12

[Sajadi]

As webextensions make progress and additional API are for sure over time introduced, that would for sure require someone who back-ports all additions - which is as i imagine a massive and complex task.

Personally i do not see that happening without someone who would help Moonchild big-time with it.

[ketmar]

i can't see anything wrong with uMatrix and Pale Moon. what GH did is removed travis-ci testing for old ff versions, that's all. Pale Moon app id wasn't removed from install.rdf, no XUL support code was removed, and i just updated my uMatrix with `git pull` (as i'm doing usually), and nothing is broken: all blocking rules are stil working, UI is here and fully functional, options page is not broken at all.

[gracious1]

i can't see anything wrong with uMatrix and Pale Moon.

Which release are you talking about? I tried to install 1.1.12 in PM 27.7.0a2 (64-bit) (2017-11-23) and I got the expected error message:


I downloaded the XPI file; there is no install.rdf. Looks like he read your post and removed the XUL/XPCOM code??

(BTW, did you mean Pale Moon or Basilisk?)

[ketmar]

i'm not following releases, and not using published xpis. i am using cloned git repository, and i'm building xpis directrly from the source. right now it is uMatrix 1.1.13b0, updated several hours ago. works like a charm.

and i meant Pale Moon, which will be ported to new platform anyway, as Moonchild said. it doesn't matter much, tho, as both browsers are using the same underlying framework, so making uMatrix UI working will be as easy as:
1. either patch uMatrix XUL overlay (several lines of code), or
2. add XUL toolbar to Basilisk, so uMatrix overlay will work (can be done with another extension, no uMatrix patches required).


as i said, what GH did is stopped publishing xpis for XUL-based framework. all the code is still there, and Pale Moon (XUL, actually) support is not removed. anyone is free to build correct xpi from uMatrix source code.

[Sun42]

Personally i do not see that happening without someone who would help Moonchild big-time with it.

True dat, but this will be the main problem in the future (same with waterfox) - backporting is difficult to do for one/few-man/men projects, and in the future mozilla won't check for for compatibility xul/we anymore. Plus when esr runs out, even more deveopment will stop and legacy addons might be (semi)hidden or even removed from amo - so that just sticking to legacy addons will be even more difficult.

Feature request: With we not fully supported, could the we extensions be marked in the addon list (the inverse of the "legacy" ff56 does)? ... at least then it would be easier to track down problems with we code that isn't completely supported on basilisk.

[coffeebreak]

could the we extensions be marked in the addon list (the inverse of the "legacy" ff56 does)? ... at least then it would be easier to track down problems with we code that isn't completely supported on basilisk.

PM's add-ons site has a validator tool to which you can upload an extension to get this information.

Or as an alternative, you could look inside the add-on with an archiver (7-zip, bandizip etc.) and check for the presence of manifest.json in the root directory, which would indicate that it's webex. See https://forum.palemoon.org/viewtopic.php?f=46&t=12503#p89424

[Sun42]

could the we extensions be marked in the addon list (the inverse of the "legacy" ff56 does)? ... at least then it would be easier to track down problems with we code that isn't completely supported on basilisk.

PM's add-ons site has a validator tool to which you can upload an extension to get this information.

Or as an alternative, you could look inside the add-on with an archiver (7-zip, bandizip etc.) and check for the presence of manifest.json in the root directory, which would indicate that it's webex. See https://forum.palemoon.org/viewtopic.php?f=46&t=12503#p89424

Thanks, though these options aren't exactly without a hassle :-p ... it's probab quicker just to look at the amo site version history, most authors specify the switvh to we or you can look at the ff compability version. Stil, a "this is we and might now work on basilisk" badge in the addon manager would be nice

[dark_moon]

Any news on this?
Even the 2017-12-28 update doesnt work with uMatrix, Decentraleyes or other.
Maybe because of Firefox 57+ as minimum. In my opinion Basilisk should support that kind of addons