sorry for minor grammatical errors.
There is invariably a problem with css - a problem that doesn’t involve the programmers or webmasters who take the (valuable) pain to work on css and provide solutions: and the problem is that the solutions always involve a considerable amount of problems and are rarely definitive.
The mere fact we must sponsor something like a “hack model” (the name tells it all) for css rules is in itself not only a nightmare, but I am also dubious we should let such things sneak into our codes wilfully. A mistake in a code is normal, but convoluted solutions sponsored and encouraged is another thing.
You script following the W3C standards and you find that a rule works on IE6 but not on IE5 yet wait on IE5 for Win ok but for mac not yet and oh well NS4 don’t even mention it, NS5 ok but not always, safari I hope you work for a big firm where you can afford the _luxury_ of testing your pages on 3 different operative systems, then Firebird (or was it Phoenix…?) which doesn’t scroll, then Opera, yes but from 7.2 onward because before 7 it didn’t work, so well this rule, put a hack here and then doesn’t work put a hack there and then works here but wait let me boot my friend’s mac and bring the diskette, wait it doesn’t work there, ok this hack but now doesn’t work where it previously worked, they released a new version of Opera let’s hurry, wait have you tried that new browser, add this line, remove that, wait a minute…
Are we being payed for doing this? A few would answer we are.
All of this in the face of what is not only called “standards” but even “recommended”.
On what basis we recommend?
On what basis we deprecate?
The W3C deprecates: but why?
Is that truly a necessary part of its work?
It seems now it has deprectaed name attributes: have server side languages taken into account while we deprecate the name attributes?
In what world do we live when we script?
Now we discover tables are not “encouraged” - yet solutions that don’t work are.
I can be wrong, but if one wants to obey to deprecations and standards and recommendations, you have to make choices: either you accept only a limited amount(though majority of users) of browsers, or you make up your mind to make impossible css rules crammed with hacks that wouldn’t eventually work in the expected way on some platform/browser combination anyway.
Deprecate, deprecate all the while… what do we get in change? I would say that deprecations are untimely - to say the least.
We work with real browsers, not with Star Trek.
Long time ago we were struggling with NS4 and the notorious “browser sniffing”. We hoped things had moved on, we now discover that we’re back to those times, with a different name.
W3C should reccomend and deprecate less. And we ought to make choices because, realistically, in this mess we JUST can’t make everybody happy! And this should be acknowledged and said frankly & openly.
It is not a matter of being a bad webmaster: it is a matter that tables are useful, and deprectaing them today to leave us with box hacks means living on a different level than the one we poor webmasters fight every day.