TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I don't see any reason why CSS can't be implemented today, even if it's
something as small as coding some text to appear in 9pt Arial and having to
settle for <FONT SIZE="2"> for people who aren't using the latest browsers.
For those people who aren't using a CSS-capable browser, it's relatively
easy -- with the right planning -- to build pages that degrade gracefully by
using the <span> and <div> tags and to have the right classes created ahead
of time. For me, the real frustration with CSS is the way Microsoft and
Netscape implement it with their respective document-object models. Each
company's different way to refer to the different objects on a page makes it
impossible to create cool, potentially useful features like drop-down menus
and expandable lists while only creating one web page. And of the two, I
have to say MS's makes more sense, from a programming perspective.