Take the 2-minute tour ×  Given this JavaScript code (which is
just a comment referring to a url):  // see
http://enterprisejquery.com/2010/10/how-good-c-habits-can-
encourage-bad-javascript-habits-part-1/  JSLint with "Safe
Subset" turned on will say  Dangerous comment.  How can a
comment be dangerous? Comments, by definition, aren't parsed! Or
are they?  Edit: Using a different url isn't necessarily
dangerous. For example this:  // http://enterprisejquery.com
doesn't trigger the flag. How can one URL in a comment be
'dangerous', but another isn't?  share|improve this question  2
Answers 2  up vote 3 down vote accepted  "Dangerous" comments
match the regular expression:   In this case, your comment is
"dangerous" because it contains the string "script".  I think
this is probably a false positive.  share|improve this answer
You're right-- this is script block paranoia. Wow, I wish jslint
would just say that. –  paleozogt Jun 14 '12 at 17:38 btw, just
doing // script triggers it. Or in the question example, re