Okay, that's it. I've had enough of the sloppy code, the workarounds, all of it.
Should I or shouldn't I go for it and give myself over to ONLY creating CSS tableless sites?
The thing is . . . What do I do if I create a beautiful, validated, state-of-the-art, CSS-only site and a prospective customer looks at it with an older browser?My suggestions is use tables for what they are intended for. Use them to display information in a table.
Honestly, if someone is use an ancient browser that does not display CSS properly, well, tough luck.
Go with CSSThe thing is . . . What do I do if I create a beautiful, validated, state-of-the-art, CSS-only site and a prospective customer looks at it with an older browser?I code for IE 5+, Netscape 6+ and Opera 5+. If they're using a previous version browser then I'd suggest slapping them before explaining to them the importance of them upgrading so that they don't get slapped again.
However, I've got some bad news for ya, there are a ton of CSS work around (mainly for IE). Enjoy.
Last I heard there is only 1% of the population using a browser which is not properly CSS compatible. And if they're not using a CSS compatible browser, there is no reason not to be, then they probably weren't a very good customer anyways.If you use properly constructed and semantically meaningful HTML markup, the page will still be usable by a non-CSS-enabled browser (though it won't look as pretty). My suggestion therefore is to get the HTML right first, then make it look nice with CSS.It will help you considerably if you use the Firefox browser with the webdeveloprs toolbar installed.
Should I or shouldn't I go for it and give myself over to ONLY creating CSS tableless sites?
The thing is . . . What do I do if I create a beautiful, validated, state-of-the-art, CSS-only site and a prospective customer looks at it with an older browser?My suggestions is use tables for what they are intended for. Use them to display information in a table.
Honestly, if someone is use an ancient browser that does not display CSS properly, well, tough luck.
Go with CSSThe thing is . . . What do I do if I create a beautiful, validated, state-of-the-art, CSS-only site and a prospective customer looks at it with an older browser?I code for IE 5+, Netscape 6+ and Opera 5+. If they're using a previous version browser then I'd suggest slapping them before explaining to them the importance of them upgrading so that they don't get slapped again.
However, I've got some bad news for ya, there are a ton of CSS work around (mainly for IE). Enjoy.
Last I heard there is only 1% of the population using a browser which is not properly CSS compatible. And if they're not using a CSS compatible browser, there is no reason not to be, then they probably weren't a very good customer anyways.If you use properly constructed and semantically meaningful HTML markup, the page will still be usable by a non-CSS-enabled browser (though it won't look as pretty). My suggestion therefore is to get the HTML right first, then make it look nice with CSS.It will help you considerably if you use the Firefox browser with the webdeveloprs toolbar installed.