CSS Lint is harmful

Re:CSS Lint is harmful by btilly on Monday July 11, 2011 @11:12AM (#2751008)

The author claims that you don't need to pay attention to advice about portability because it isn't that hard. And then makes the article look bad from my OS X notebook because he couldn't use single quote characters in a font that that, you know, actually renders.

[ Parent | on HN ]

Re:CSS Lint is harmful by MattWilcox on Monday July 11, 2011 @11:20AM (#2751050)

Hi, I'm Matt. I can only apologise for the site and your poor experience using it. The design/html/css is about 5 years old, and the core of the site is hand-coded from the ground up (WordPress didn't exist when I built it some 9 years ago).

The HTML/CSS hasn't been updated in that time, except to stop enforcing the XHTML Strict Mime type. I'm aware of how poorly the site reflects my skills and how out of date it is. But, at least it works accessibly - if a dodgy glyph on a browser that didn't exist when it was built is the only issue, I'll roll with that.

[ Parent | on HN ]

Re:CSS Lint is harmful by tjogin on Monday July 11, 2011 @01:07PM (#2751542)

The problem is that you haven't specified a charset, so the browser just uses its default setting, sometimes causing problems when the default is anything other than ISO Latin-1.

Fix the problem by specifying the charset in your HTML markup.

[ Parent | on HN ]