The release of the NoScript 11.2.18 browser add-on has been formed, designed to block dangerous and unwanted JavaScript code, as well as various types of attacks (XSS, DNS Rebinding, CSRF, Clickjacking). The new version fixes an issue caused by a change in the handling of file:// URLs in the Chromium engine. The problem resulted in the inability to open many sites (Gmail, Facebook, etc.) after updating the add-on to version 11.2.16 in new releases of browsers using the Chromium engine (Chrome, Brave, Vivaldi).
The problem was caused by the fact that in newer versions of Chromium access to the URL "file:///" was denied by default. The problem went unnoticed as it only appeared when installing NoScript from the Chrome Store add-ons directory. When installing the zip archive from GitHub through the "Load unpacked" menu (chrome://extensions > Developer mode), the problem does not appear, since access to the file:/// URL is not blocked in developer mode. As a workaround, enabling the "Allow access to file URLs" setting in the add-on's options works.
The situation was exacerbated by the fact that after the release of NoScript 11.2.16 in the Chrome Web Store catalog, the author tried to cancel the release, which led to the disappearance of the entire project page. Thus, for some time, users could not roll back to the previous version and were forced to disable the add-on. The Chrome Web Store page is now back up and running and the issue is fixed in the 11.2.18 release. In the Chrome Web Store catalog, in order to avoid a delay in reviewing the code of the new version, it was decided to roll back to the previous state and place the release 11.2.17, which is identical to the already tested version 11.2.11.
Source: opennet.ru