Cory Shubert wrote: > http://www.nwaworldvacations.com
> We tried to do a better job of CSS and moved into a more Web 2.0 > vibe, at least that is what we were trying for. I am sure many will > lament our use of tables still, but some habits die hard. I am > curious to learn how we might have done a better job with our CSS, > i.e. better use of IDs or Classes, less nested, more nested... Those pages don't work well with resized fonts in any browser, and absolute font-sizes don't make it better since one has to 'ignore font size in page' in IE/win in order to resize. The table layout don't work too well if one wants a printout either, so different styles for different media - and a lot of testing, seems necessary. Pages have quite a large file-size when one looks at the amount of content it carries, and attempts to slim down the source code should be made. The use of paragraphs with non-breaking spaces as "layout-spacers" equals the use of old spacer-gifs, and should be avoided. Use margins and/or paddings instead. The "verisign" at the bottom doesn't seem to work as intended outside IE/win. The use of inline styles should be discontinued once you've added a stylesheet, as inline styles tend to make debugging and general maintenance harder and more time-consuming. If page-specific styles are needed, it is usually better to group those in a style-element in the page-head. The usability of such a site may be evaluated to a high degree by running it through a text-only browser like Lynx... <http://www.delorie.com/web/lynxview.html> <http://lynx.isc.org/> That's the basic level a well-built site should be able to work at no matter what, so testing your site in Lynx will give you a good sense of what works and what doesn't. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
