Re:Designing for A Retina Web
by jlgreco on Monday August 20, 2012 @07:18PM
(#4410299)
Icon fonts just seem to like such a hack to me in a world where SVG exists. Is the entire idea behind using them just that IE 7/8 doesn't have SVG support? How did lack of SVG support even happen? SVG seems like something any modern browser should have had for years.
[ Parent
| on HN ]
Re:Designing for A Retina Web
by yusefnapora on Monday August 20, 2012 @07:27PM
(#4410335)
Android also lacked SVG support until 3.2. The justification I read was that they deliberately disabled it from their webkit build to save 1MB in the compiled binary. Sad, especially since pre-ICS phones are by far the most prevalent.
Re:Designing for A Retina Web
by justincormack on Tuesday August 21, 2012 @04:41AM
(#4411748)
Although a low Res image fallback is OK there.
I would love to use SVG, but support just isn't robust enough. Hard to deal with hover/active states too. Icon fonts are one request and easy to style with CSS color and text-shadow (even simulating glows). I just wish there was an easy way to generate a small font set from a the handful of vector elements I need for a given website (custom elements, that is, not using a service like Pictos).
You can hint a font. You can't hint an SVG.
Huh, that is unfortunate. Is hinting still important on devices with such high DPI though?
Re:Designing for A Retina Web
by Chris_Newton on Tuesday August 21, 2012 @06:14AM
(#4412037)
It’s not usually the high-dpi devices that you’d be adding hints for. The point is that anything that is going to replace today’s pixel-perfect bitmap graphics still has to look pixel-perfect when rendered on lower-dpi devices, which is going to remain by far the majority of visitors to most sites for a while yet.