No, really. Think this is intentional? I mean, you'd think the Chrome developers know what JSLint is. You'd think maybe they could sneak in an exception for it...

 

Either way, this doesn't bode well for JSLint's usage rate.


Labels: ,