@
philip_clarke:
NoScript
by default is tuned to check for injections only when it's necessary, i.e.:
1. The request must be cross-site (this can be overridden by setting noscript.injectionCheck to 3, which will cause NoScript to check every request, even same-site)
2. The target site must be Javascript-enabled (XSS won't work anyway if it's not). Of course, some "dangerous" HTML injections are checked also if the target is not Javascript-enabled yet, as sirdarckcat showed you, and if you allow the site after the request it gets checked during the reload.
3. The target site must not match any of the exceptions listed in
NoScript Options|Advanced|XSS. This includes by default Google Search, Yahoo! Search and Wikipedia articles, because they're likely to contain sensible patterns, (especially if user is a coder), but are proven to be safe. Of course you can remove them, if you feel like that.
All the cases you reported as false negative were either same-site (not XSS) or non-whitelisted target (injection won't run).
The noscript.net site triggers because it's included in the default whitelist shipping with NoScript, therefore if it
was vulnerable it would need to be protected.
--
*
hackademix.net*
There's a browser safer than Firefox... Firefox, with NoScript