After following this thread for years, I wanted to know what changed. Did Chromium make changes to allow more of NoScript's features to be implemented? Were there some compromises made for the Chrome version? How has NoScript adapted to WebExtensions and Chrome? I'm not generally familiar with WebExtensions. So maybe there is some basic assumption I'm missing. But here is what I've been able to piece together.
https://www.ghacks.net/2019/04/12/firef ... or-chrome/Mozilla paved the way for a cross-platform NoScript extension when it turned off the classic extension system in Firefox 57. The organization selected WebExtensions as the new system for Firefox which, among other things, ensured compatibility (to a degree) with Chrome extensions.
https://www.zdnet.com/article/noscript- ... le-chrome/"Talking about differences across supported browsers, the code base is now is exactly the same," Maone told ZDNet.
https://hackademix.net/2019/04/12/cross ... ome-store/One difference Chromium users need to be aware of: on their browser NoScript's XSS filter is currently disabled: at least for the time being they'll have to rely on the browser's built-in "XSS Auditor", which unfortunately over time proved not to be as effective as NoScript's "Injection Checker". The latter could not be ported yet, though, because it requires asynchronous processing of web requests: one of the several capabilities provided to extensions by Firefox only.
From my reading, it seems like the advent of WebExtensions on Firefox coaxed the NoScript code in the direction of Chrome. But it is not clear to me how these historical problems were resolved.