When you buy something, I bet you want it to work. Heck, even if you use something for free — maybe borrowed from a friend — I bet you want it to work. No one prefers hiking boots that are too tight (or too loose), a car that shimmies when you drive faster than 40 miles an hour, or a kitchen knife that can’t cut a tomato. And Web designers don’t prefer fonts that don’t fit a project, fall apart in different browsers or can’t be used in a mock-up. We also don’t like wading through all of the fonts that won’t work for us in order to find the ones that will . It takes precious time away from other tasks and responsibilities. You’ve Come A Long Way, Baby! Six years ago, A List Apart published “ CSS @ Ten: The Next Big Thing ,” in which Håkon Wium Lie describes the @font-face declaration and announces: “Two things must happen before Web fonts can take web design to the next level… First, we must ensure the validity of the approach.… Second, we must convince browser makers to add support for web fonts.” You Helped Make It Happen: Validity and Browser Support Today, browsers support Web fonts, and we’ve got the valid CSS to make the fonts work. Of course, as old browsers changed and new browsers (and extended font families) emerged, valid CSS became an ever-moving target
↧