Those of us who were around and hard at work in the mid-1990s knew about CSS and prayed fervently for it to be implemented sooner and more effectively than it was. To make a long story extremely short, programming for the Web in the late ’90s sucked because it wasn’t.
Ten years on from the ultimate peak of “irrational exuberance,” we now have better CSS. Still, it’s not always so good at coping with the requirements of the contemporary Web. Its truly rough patches are described in the following sections.
As design elements go,
are elegant. They provide an additional mechanism for narrowing scope
via the cascade, which is awfully elegant on its own.
Unfortunately, they’re poorly supported. Consider:
@import rules might or
might not be applied by a given browser, depending on how they’re
written and where they’re located in the source order of a document
@media rules can take on additional, vendor-defined, arbitrary
that usually want for clear documentation.
Support for alternative media properties leaves a great deal to be desired, as discussed in Chapter 3.
they’re great, but when they don’t, they…don’t. Some of the
features discussed here might pop serendipitously into your psyche
and save you several hours of labor during a death march, but it’s
very unlikely that
ever be among them.
Every visual display medium has a fundamental unit of length, ...