On 6 Sep 2006, at 12:13, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
I often find myself using 'functional' class names for a handful of
specific tasks, but often these are used in parallel with semantic
class
names, for example:
<div class="navBar noPrint">
.noPrint has only one simple rule, which I know will never change.
Similarly I occasionally use .leftAlign & .rightAlign but again only
with very simple rules that won't change: visually styling is done by
other means.
Surely the question of whether .navBar will print or not has nothing
to do with the content, and has no place in the markup?
Assuming .noPrint means "Don't output on a printer", a print
stylesheet containing
.navBar {
display: none;
}
will make explicit what you are doing, and means you don't have to
put information about how the document is presented _in certain
circumstances_ into the document itself. Otherwise you could finish
up with your document littered with classes for handling its
presentation on a wide variety of media (screen, handheld, aural,
projection, not-yet-invented), which is exactly the kind of creeping
presentationitis CSS was specifically designed to avoid.
Just my 0.02GBP,
Nick.
--
Nick Fitzsimons
http://www.nickfitz.co.uk/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
