Hi Everyone! I was just looking at a very ugly hack someone posted here recently which proudly announces at the end "this hack is valid CSS3". Well, great. Does that mean that whatever flaw in the target browser (in this case Safari) the hack was used to work around will bring other browsers to their knees when they catch up in CSS support? Not a great approach to web site building.
I am not anti-hack. I use "* html" in pretty much every stylesheet I write. But I think hacking for current leading-edge browsers is a bad idea, unless you are compensating for some major lack of support that other browsers have (eg no min-height in ie6-). Only use hacks that can do no harm in the future (I don't use the underscore hack, but it's a safe one, as it's unlikely other browsers will suddenly start supporting it.) And as for "valid CSS" - I could care less. "zoom:"? "filter:"? Ok, if it works. Valid HTML - yes, please. That's future-proofing. But isn't CSS where we shunt all the complexity and ugliness that used to be in the markup? One day there may be an elegant and easy-to-understand layout language, but sadly CSS ain't it. Aiming for valid CSS is fine, and won't it be nice when it's all we need? But we mustn't fool ourselves into thinking that if it validates we can't have done anything wrong. -- Chris Ovenden http://thepeer.blogspot.com "Imagine all the people / Sharing all the world" ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
