When you go through 13 rounds of changes with a client and discuss things like the letter spacing on single superscript letters then you just might have to put in the odd hack.
Browsers render differently, and while we might all like to say that hacks are bad and not needed I think that is a disservice to people just learning to use CSS-p for layouts.
When I was learning css part of learning all the browser quirks was learning how to get around them, but you cannot learn all that at once and sometimes you need to focus on learning part A properly before you move on to part B.
Hacks should be minimised, and the focus should be on hacks that are less likely to fail in the future. But there are times when they are NECESSARY. At least during the learning process but to some extent even after one has mastered some css.
Clients and the many print trained art directors want pixel precision... sometimes this means using hacks, unless we forget the whole thing about not having to edit the html and start modifying the structure half the time instead.
s
Hacks are for the Cowbot webdesigner who hasnt done his job right in the first*****************************************************
place! ( or for a client thats given too much hassle and not enough cash to make
the recode cost effective! ;] )
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
