All using the same blog template is definitely not in the same ballpark as overriding default browser behavior with something that doesn't work.
It's not even the same sport..
Edit to respond to your revised comment that replaced its content with the title of your article (wow, way to be accepting of criticism, dude! When you do usability testing and a user finds a bug or complains about something, do you tell them they're an idiot, too?):
Even if it's a bug in Chrome's rendering engine, you have an IE7 specific stylesheet, assumedly to support the bugs in its CSS rendering engine. And considering IE7 usage is 11.7% while Chrome's is 10.8% [1], you've just alienated a fairly large portion of your potential readers.
So you suggested he not be an asshole and it offends you he proposes you cease being an idiot. It's the sort of discourse that promises further Great Insights.
Asshole behavior is markedly different than idiot behavior ;) I fully acquiesce that my comment was, itself, asshole behavior - I wrote it in an emotional state, as a usability/UI design blog that breaks a basic tenant of web usability (don't override basic browser behavior; if you have to, make sure it works everywhere because people expect it to be there - they get upset when things happen that they consider breakage) was a fairly intense mind-breaking experience.
Calling someone an asshole is asshole behavior. Knowingly forcing your users into a broken usability situation is asshole behavior.
I wouldn't think that calling someone out on it would be considered idiot behavior.
