After my little rant yesterday I decided none the less to try my hand at the implementation of a no-tables-for-support layout once again. This time around it seems to work quite well, though time will tell if any reports about compatibility issues reach my ears in the near future. This once again entitles me to use this:
Update: This will never end! I discovered a few glitches caused by the use of a div based layout that I decided were unbearable to live with. As a result I’m now back to a single 2 celled table which holds the content and sidebar where they’re supposed to be… I feel dirty ;)
You probably hate my site then. :) Nothing but tables (too lazy to learn CSS). If I ever decide to change the site’s layout, those tables are going to be a bitch to update.
Indeed. My new layout isn’t 100% right yet either. Tables are an easy way out of these thing, but there is a great deal of satisfaction in being able to control all the layout on the entire site from one single CSS file :)
I totally get nothing? Explain!
Get nothing out of what exactly? Of why tables are a no-no in layout or why div’s are a monumental frustration in layout?
Still no propeller hat?
Propeller hat?
Sigh, I thought you’d remember… :-) A few days ago we drew a parallel between yours and Calvin’s impatience, regarding word from I/O, and a propeller hat, respectively…
I was just being curious – in a silly way – as to wheather you’d heard from I/O or not.
But then again, since it’s not plastered all over your site, I already know you haven’t… ;-)
I don’t get it, what is it about you and tables? Ever heard of the expression; “If it ain’t broke, then don’t try and fix it”. Tables work, and they offer a greater compability for users and if it looks the same or better, why don’t just stick with them? :-)
Why use semantically correct code? Well for a variety of reasons.
1) Longevity – When my code is dug up many years from now without it’s accompanying stylesheet it will retain it’s readability due to the fact markup was used in the fashion it was intended for. This does not cover merely the use of headers, but also the table element. This is for a variety of reasons
2) Cross-browser and device – If you stay within the realms of standards and semantically, that is structurally correct code, chances are that your site will be capable of showing in next generation browsers as easily as it will in current generation as well as last generation. And on top of that it’ll probably degrade easily to for instance a PDA or phone if needed and whatever else that you haven’t thought of which might appear sometime in the future. And I’ll even throw in a good example.
3) Accessibility – While probably not all that relevant for this particular site, there is no harm in making sure that handicapped people have as much of an advantage as I can give them when they happen to come by. Nested tables and cluttered HTML 4 font tags and what have you certainly don’t help much.
4) Extensibility – If using div’s only, the idea is that the entire design, including all elements can be changed around using only the CSS. As soon as I start taining my structure with div’s for layout and not for data for which a table is actually needed, that ability deminishes fast.
There is nothing wrong in terms of correct use of XHTML (or HTML for that matter) if you use a table for layout. But there are levels of greatness when it comes to code structure, and using tables is not a ‘good thing’.
Read more here and here and of course here.
And certainly this.
we are the biggest exporter of bonsai tables(stands),
if you are interested in our products,please contact us.
Best regards.
LOL! What a perfect example of a search gone wrong. Mr. Frank here probably searched for Bonsai Tables, and then got to a page that has nothing to do with bonsai other than the name, and an entry talking about HTML tables…
More a perfect example of comment spam :), I’m going to disable the link and let this stay here just for the comic value :D