[TheRedEye]

Right, that's exactly what he's saying. In the old days we all did it because browsers would stretch the equivalent of "nearest neighbor," but they haven't done that for a long time now.

[ICEknight]

Have you guys tried putting this in the CSS?

img {
image-rendering:optimizeSpeed; /* Legal fallback */
image-rendering:-moz-crisp-edges; /* Firefox */
image-rendering:-o-crisp-edges; /* Opera */
image-rendering:-webkit-optimize-contrast; /* Chrome (and eventually Safari) */
image-rendering:optimize-contrast; /* CSS3 Proposed */
-ms-interpolation-mode:nearest-neighbor; /* IE8+ */
}

[Xkeeper]

That's close to what TCRF uses and I can verify that Chrome flat out ignores that (I'm subscribed to a bug entry about it, even).

Given that Chrome is a pretty big share of browser space these days... yeah.