Even if a new platform in the future might theoretically allow the use of WebExtensions, Pale Moon's application code will not.

As such, it would require a (messy) compatibility layer to enable insertion into our XUL-based UI, and likely will cause many many bugs. Pale Moon's front-end doesn't use UI controls or layout that allows html-based widgets (the only way for WebExtensions to interface) to be inserted.Adding a 4th technology to that line-up that is radically different and more limited in what it can offer by design is a maintenance nightmare and time-sink we simply don't want in our project. Having XUL/overlay, bootstrapped and SDK/PMKit extensions already provides everything any extension developer could want or need for extension development, and then some.Pale Moon (as an application) will likely never support WebExtensions, even if we would switch to a platform that technically supports its use, because:

You can compare them with Jetpack/SDK extensions, but then without having the option to even call into lower level functions.

WebExtensions are the (chrome-sourced) type of extensions to web browsers using a very limited subset of APIs available through a framework.

Pale moon greasemonkey