Jeff Cochran wrote
| Timo Breumelhof wrote
But most browsers don't interpret these classes correctly, which could be a reason to change the classes if possible. (has to be researched)
|
Or a reason to change the browsers. :)
Which is one of the issues with pure CSS design. As opposed to tables, you're bound to run into more browser workarounds, simply because tables have been around long enough that browser support is nearly identical. But this is the same argument that started when HTML was introduced as an alternative to SML. Or when some browser versions didn't support tables. When a single pixel GIF file sufficed for indentation and spacing. The same argument that will take place when ABCML replaces XYZML as the fourth dimension of web browsing.
Given time, browsers and CSS will work as intended when the concept was first published as an RFC.
Jeff
Change browsers? No, you should change your code to work in all browsers. The web is about the users, not you. Your site should work for as many people as possible given your budget and research based on your target audience's browser statistics.
And as for workarounds and problems with CSS, you have an insufficient knowledge of CSS, then. With correct doctypes, almost all CSS problems disappear in the major browsers. Why use a spacer.gif when you can use padding?
Sorry dude, but you need to read more about CSS and semantic (X)HTML.
Just because you can't figure out the right code to use to make your layouts work doesn't mean you should use terrible code. You should read up on how to do it properly.