by  creed3

Just quickly, in the world of CSS and visual web site presentation, I wonder how many designers are of an all-or-nothing mindset, meaning you abandon much of all HTML page layout and use only CSS.  I have tried countless times to take that approach only to discover you often you end up with a ridiculous amount of CSS due to the lack of uniform browser adoption (no thanks to the biggest offender Microsoft) to achieve what simple HTML has done in all browsers for years now.  A really good example is tables, which are straightforward and can be very complex in HTML, and can quickly become a nightmare in CSS.  Oh sure, there is a crude table option in CSS, but why go there when it’s not supported in all browsers and HTML is?  Thoughts?

Follow comments on this post with this RSS 2.0 feed.
Leave a comment, or trackback from your own site.

there are 2 comments

straight from the technology of Doug Webster
02.05.2015 at 6:22 pm

I’ve been using Normalize.css for a while now. I like it because it doesn’t reset everything, it just makes behavior more consistent across browsers.

I try to use HTML and CSS in ways they were intended and avoid “hacks”. So I’ll use tables for presenting information in a table style, but not use tables (often nested) in order to layout a page. I also, in as much as is possible, try to allow elements to be flexible (avoid fixed widths, heights, etc.) and allow them to flow naturally in HTML. This helps significantly in making sites responsive and adaptable to changes in content.

Fortunately present browsers, including IE, do a lot better job of supporting HTML and CSS and are more consistent than they use to be in the past. There are many things which are practical to do now with CSS and HTML which wouldn’t have worked several years ago. is helpful in figuring out browser support of various things.

straight from the technology of creed3
02.06.2015 at 9:08 am

I agree Doug, I avoid hacks at all costs. Those can often spell trouble later on as browser support and the standards evolve. I also avoid using support code when ever possible. Not that helpers like normalize.css are bad, I just prefer to keep everything as small and quick loading as possible. I suppose this goes back to the days before broadband when even 2k made a huge difference in page load times. Yet I also try to keep in mind that broadband is still somewhat limited to populated areas and many small towns still rely on dialup.

I too avoid fixed widths when ever possible, which is easy to do as most widths can be completely flexible and still maintain a consistent layout.

You’re correct that browser support is FAR better today than even a few years ago. IE was always the worst offender of not supporting the rules they themselves help to create. Not having Windows at my disposal I’m a bit behind the curve on what the latest version does. Of course while current browser support makes life much better for us, it doesn’t solve the problem of legacy browsers, which in some cases older computers have no choice but to use. I tend towards the idea of designing with the latest support in mind. If I can support an older browser without miles of code I will do so. Those who are stuck using an older version of IE can opt for another browser though, so my concern for legacy support is not very high.

Thanks for the tip on ´╗┐ That’s one I hadn’t run across yet.

You must be logged in to post a comment.

. . :   design & hosting by   : . .