View previous topic :: View next topic |
Author |
Message |
TheRedEye The Internet's Frank Cifaldi
Joined: 26 Aug 2003 Posts: 4192 Location: Oakland, CA
|
Posted: Wed Sep 05, 2012 4:12 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
ICEknight
Joined: 15 Dec 2003 Posts: 569
|
Posted: Wed Sep 05, 2012 11:09 pm Post subject: |
|
|
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+ */
} |
|
Back to top |
|
|
Xkeeper
Joined: 04 Nov 2005 Posts: 327 Location: Henderson, NV
|
Posted: Thu Sep 06, 2012 1:15 am Post subject: |
|
|
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. |
|
Back to top |
|
|
|