As to NoScript: - from a linked Mozilla blog post: > [...] A major challenge we face is that many Firefox add-ons cannot possibly be built using either WebExt

As to NoScript: - from a linked Mozilla blog post: > [...] A major challenge we face is that many Firefox add-ons cannot possibly be built using either WebExtensions or the SDK as they currently exist. Over the coming year, we will seek feedback from the development community, and will continue to develop and extend the WebExtension API to support as much of the functionality needed by the most popular Firefox extensions as possible. [...] (https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev...) - then, from a link posted at the end of the Mozilla blog post (in an "Update" section): > [...] One concern people have is that their favorite add-on is no longer going to be supported, especially add-ons for power users. Some of the ones being mentioned are: > [...] NoScript, [...] > We’re working with Giorgio Maone, the developer of NoScript, to design the APIs he needs to implement NoScript as a WebExtension. [...] (https://billmccloskey.wordpress.com/2015/08/21/firefox-add-on-changes/ https://billmccloskey.wordpress.com/2015/08/21/firefox-add-o...)