NoScript 10 supports content blocking and XSS protection just like its legacy counterpart. The main reason why that is not the case yet is that APIs are still not available that NoScript requires for some of its functionality.

While it is released as a WebExtension so that it can be installed in Firefox 57 and newer versions of the web browser, it is not a complete one-to-one copy of the legacy add-on. It is still recommended to go through the preferences once to make sure they are set correctly, and to make adjustments as you see fit. The main purpose of hybrid extensions was to make the migration from the legacy add-on system to the WebExtensions system as smooth as possible.Įxisting NoScript users will have their settings and preferences migrated to the new version that is good news as you don't have to configure the new version of NoScript after the update to version 10. Giorgio released a hybrid extension of NoScript earlier this year. Note: It won't work on Android right now, and does not work in private browsing mode either. NoScript 10 did not make it in time for the release of Firefox 57, the first version of the web browser that supports only WebExtensions and no longer the legacy add-on system of Firefox 56 and earlier versions.īut, the extension that is compatible with Firefox 57 and newer is out now, and users can finally install it on their devices if they have updated their systems to that version of the browser already.

NoScript 11.4.25 download