CSS vs tables
I’ve often been criticised for using tables in my website. I only really use them where I’ve found it necessary, but never-the-less, one table is often one too many for some. “Bad design”, etc, etc.
Well, I’m working on a re-design of the Copy+ site and have been attempted to banish tables from the site entirely. All looked well as I tested it in IE. Then Firefox. Oh my. It was a real mess. I tried to sort it, I really did, but eventually became stuck.
A post to discussion board yielded the following answer.. “the top menu ‘catches’ on your logo_box DIV.” The answer is to add “clear: both;” to my DIV.
So I asked how I was supposed to know this. The answer…
Same way as me. You do something, it doesn’t work, so you google it!
I use it so often that I have it defined as a constant in my PHP.
The other thing that I have done is that I get so fed up of fudging inconsistencies between browsers that I now detect the user’s browser and give them an appropriate css file, not a jack of all trades with indecipherable hacks in.
The conclusion… I’m not supposed to realise this. Instead I have to hack about to get the DIV’s right, probably losing sleep and hair in the process.
But, if I use tables I can get it right first time, without any of the above. Hmmm. Guess what I’m now doing to the new site??
Related posts:
- Stop Me and Buy One A new year and lots more web work. First of all, and the biggie, is adding on-line ticket sales to the BMTG site. All of...


