Revisiones de NoScript
NoScript por Giorgio Maone
Revisado por Usuario de Firefox 13446037
Se valoró con 3 de 5
por Usuario de Firefox 13446037, hace 8 añosWebExtension is a big change, so former NoScript is dead and NoScript 10 is just a new extension.
Hopefully the developer will probably recover some advanced features of the XUL version, but it will take time we must be patient.
As today, there is no alternative on Firefox 57.
It seems that developer of the excellent ScriipSafe on Chrome Webstore doesn't want to port it on Firefox.
He could have done this for Microsoft Edge since a long time, and nothing has been done.
And surfing without a script controller is I M P O S S I B L E
.
I just don't understand why Mozilla team has not developed a basic embedded javascript manager as it was in the very good former Opera 16 (presto engine), so it could have let all the time to the third party developers to create a more advanced extension.
This is not acceptable, THIS IS A VERY BIG FAULT from Mozilla.
The main issue I could address now to the developer is :
1) no possibility to grant authorization to a full domain (this is a big difference with ScripSafe which lets the choice to the user)
Example : I want to authorize domain and all subdomain of the CDN provider Akamai, This si possible with scripsafe by using the "trust" option instead of "allow", it is not possible here
I want to authorize all Akamai because due to load balancing process the CDN server may change a lot, and so you still need to allow various subdomain. Maybe the developer could implement very quickly a joker system allowing to enter domains like :
*.akamai.net
*.hd.akamai.net
In first case we allow every subdomain of akamai.net
In the second case we limit to every subdomain of hd.akamai.net
2) No synchornization option
Ideally, NoScript should store the users data in cloud through the Firefox account as ScripSafe does in the Google Account.
But maybe it is not possible according to the Firefox account policy, so the workaround should be to be able to synchronize data to/from a local path on the computer.
One just have to create this path in a OneDrive or Google Drive synchronized directory...and this should be done.
I have several computer, each computer has several users session, this is just annoying to set up NosSript for each repeating always the same process. And when I set up a new computer, I must restart from the beginning.
With ScripSafe, this is very easy... the extension automatically download and upload to Google Accounts (one must activate such option).
If ScripSafe is ever ported to Firefox with the same functionalities, I drop NoScript
3) Slow GUI
As today, the NoScript GUI is I N C R E D I B L Y slow.
As a comparison ScripSafe is incredibly fast to display the distant hosts list
But this version is a kind of quick done dirty version, let's be patient, this will be probably fixed in the future, but developer must know that the situation is as today not acceptable. I also suspect that NoScript 10 slows down the browser
4) Inefficient filtering mechanism
In the former XUL extension, the filtering engine of NoScript was crappy as it was oftenly forgetting a lot of distant host.
So one needed sometimes to switch to "allow all scripts" to see these hosts, and go back to "forbide all scripts", and so we could set rules for theses invisible hosts.
As compared, ScripSafe was far better as there was not such issues.
Finally.... XUL NoScript is dead and this is a very good thing because the filtering engine of NoScript was outdated and the author didn't want to admit that.
Let's see now if this brand new Web Extension addresses such issues, I can't say at this moment.
Hopefully the developer will probably recover some advanced features of the XUL version, but it will take time we must be patient.
As today, there is no alternative on Firefox 57.
It seems that developer of the excellent ScriipSafe on Chrome Webstore doesn't want to port it on Firefox.
He could have done this for Microsoft Edge since a long time, and nothing has been done.
And surfing without a script controller is I M P O S S I B L E
.
I just don't understand why Mozilla team has not developed a basic embedded javascript manager as it was in the very good former Opera 16 (presto engine), so it could have let all the time to the third party developers to create a more advanced extension.
This is not acceptable, THIS IS A VERY BIG FAULT from Mozilla.
The main issue I could address now to the developer is :
1) no possibility to grant authorization to a full domain (this is a big difference with ScripSafe which lets the choice to the user)
Example : I want to authorize domain and all subdomain of the CDN provider Akamai, This si possible with scripsafe by using the "trust" option instead of "allow", it is not possible here
I want to authorize all Akamai because due to load balancing process the CDN server may change a lot, and so you still need to allow various subdomain. Maybe the developer could implement very quickly a joker system allowing to enter domains like :
*.akamai.net
*.hd.akamai.net
In first case we allow every subdomain of akamai.net
In the second case we limit to every subdomain of hd.akamai.net
2) No synchornization option
Ideally, NoScript should store the users data in cloud through the Firefox account as ScripSafe does in the Google Account.
But maybe it is not possible according to the Firefox account policy, so the workaround should be to be able to synchronize data to/from a local path on the computer.
One just have to create this path in a OneDrive or Google Drive synchronized directory...and this should be done.
I have several computer, each computer has several users session, this is just annoying to set up NosSript for each repeating always the same process. And when I set up a new computer, I must restart from the beginning.
With ScripSafe, this is very easy... the extension automatically download and upload to Google Accounts (one must activate such option).
If ScripSafe is ever ported to Firefox with the same functionalities, I drop NoScript
3) Slow GUI
As today, the NoScript GUI is I N C R E D I B L Y slow.
As a comparison ScripSafe is incredibly fast to display the distant hosts list
But this version is a kind of quick done dirty version, let's be patient, this will be probably fixed in the future, but developer must know that the situation is as today not acceptable. I also suspect that NoScript 10 slows down the browser
4) Inefficient filtering mechanism
In the former XUL extension, the filtering engine of NoScript was crappy as it was oftenly forgetting a lot of distant host.
So one needed sometimes to switch to "allow all scripts" to see these hosts, and go back to "forbide all scripts", and so we could set rules for theses invisible hosts.
As compared, ScripSafe was far better as there was not such issues.
Finally.... XUL NoScript is dead and this is a very good thing because the filtering engine of NoScript was outdated and the author didn't want to admit that.
Let's see now if this brand new Web Extension addresses such issues, I can't say at this moment.
2416 revisiones
- Se valoró con 5 de 5por Ryan Steed, hace 2 días
- Se valoró con 2 de 5por Wewe Never, hace 3 díasIt doesnt remember changed levels, and 90% of all sites i visit needs permission. Javascript is everywhere I guess. Deleted the addon.
Respuesta del desarrollador
publicado el hace 3 díasIf you flag sites as TRUSTED rather than Temp. TRUSTED, permissions are remembered. Otherwise it's a bug, probably with your browser configuration, and should reported at github.com/hackademix/noscript/issues thanks. - Se valoró con 5 de 5por ZeroUnderscoreOu, hace 13 días
- Se valoró con 5 de 5por 鼎针皮艺, hace 20 días
- Se valoró con 5 de 5por Bob, hace un mes
- Se valoró con 1 de 5por mlatpren, hace un mesIt does a great job at blocking, but is regularly frustrating with re-enabling things. It's supposed to show you what it's blocking, but that's extremely hit-or-miss. Occasionally, there'd be something blocked where the only solution is to disable the extension. As in, right-click and disable *from Firefox itself.*
- Se valoró con 3 de 5por zekromVale, hace un mesThere needs to be a CPU limit on this extension, using 30% CPU of an intel i7 11th gen laptop CPU on YouTube is ridiculous. Firefox for Ubuntu snap, flatpack, or just .deb are affected. Must disable NoScript to fix it or allow everything fully for all domains on the page. I would like more domains to be added to the global trusted list though (by default) or have a popup at the top when you first visit a page.
- Se valoró con 5 de 5por Hopeavirta, hace un mes
- Se valoró con 5 de 5por Lazy Cat, hace un mes
- Se valoró con 5 de 5por sumobunny, hace un mes
- Se valoró con 5 de 5por Zelgadis-San, hace un mes
- Se valoró con 5 de 5por Dadou, hace 2 meses
- Se valoró con 3 de 5por aq, hace 2 mesesUser for at least 15 years, Something is conflicting on Firefox. It is blocking scripts and other add ons such as tampermonkey or violentmonkey with scripts added, but without any listing of what is being blocked. Only option is to shut it off to proceed.
Even blocking games internal scripts without any 'monkey' in use.
Please check and test - Se valoró con 5 de 5por Simon Bünemann, hace 2 meses
- Se valoró con 5 de 5por ADKFZ8O, hace 2 meses
- Se valoró con 5 de 5por Marw, hace 2 meses
- Se valoró con 1 de 5por aedgsegsfvw, hace 2 mesesWARNING! Causes crashes with SEVERE data loss. Since mid 2025, this extension regularly causes the browser to crash. It can even crash the browser so severely that windows freezes irreversibly, with SEVERE data loss as a result. The crashes stopped when I deleted this extension, and re-occurred after reinstalling it. Several others have reported the same issues on user forums.
- Se valoró con 2 de 5por Usuario de Firefox 15990777, hace 3 meses
- Se valoró con 5 de 5por Arman Daneshjoo, hace 3 meses
- Se valoró con 5 de 5por elmika, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 19469020, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 14500718, hace 4 meses
- Se valoró con 5 de 5por Usuario de Firefox 19459487, hace 4 mesesI'm notified every time WebGL is blocked on each page load. There's no way to disable these notifications and it's very irritating.
Edit: updated to 5 stars as it can be disabled after all but the setting isn't described very clearly.Respuesta del desarrollador
publicado el hace 4 mesesYou should not get any notification. Just a little placeholder inside the page, to be able to enable it back. And you can disable it by unchecking "NoScript Options>Appearance>Show synthetic placeholders for invisible capability probes" - Se valoró con 5 de 5por Cello, hace 4 mesesit's 5-stars, because it's little time and effort to manage and also Edward Snowden said that noscript is the best protection in the whole internet...(after some Firefox update, noscript does seem to block internet in Firefox,,, but I'm sure there will be a workaround in the next edition ... buona vacanza)