No.Balia wrote: Doesn't NoScript need to identify all the script blocks to disable them in one way or another?
It just needs to identify its origin (for 3rd party scripts) or the origin of the document for the inline ones.
No.Balia wrote: Doesn't NoScript need to identify all the script blocks to disable them in one way or another?
@Thrawn: OP is using some version of Firefox 25 which was several releases before Mozilla dropped CAPS. The only way this could have been a NoScript bug in the beginning is if the OP was using NoScript 2.6.8.18.Thrawn wrote:What was the earlier version that you were using? Firefox changes have sometimes broken NoScript's ability to block inline scripts recently, and Giorgio had to work around it, so if you were using an older NoScript with a newer Firefox, then you may well have had issues.