Mark Alexander
Senior Member
Levi said:Note - not a web designer but I have done (and am doing new one) my site
But what happens if 'your' work ends up being sent to a new person as you're not the chosen coder anymore. It's fine that your work is faster for 'you' but it could end up costing the client more if they go elsewhere as it would be slower for themn. The whole point of these web standards is as far as I know to make it simple for web sites to be transferred between coders as the clients wants.
You could also argue that by not following standards you are artificially locking a client into 'your' work and this can't be good for client referrals once they figure out what you're doing, especially if one of your clients goes for a quote from someone else and finds out the issue and gets informed of the problems it may cause.
You also seem to be forgetting the benefits of a fast loading site in terms of seo, Jaz will know more, but google (and I assume bing) aslo include speed of the site as part of their criteria now. The site that started this discussion off showed just how slow tables can be and this would have a detrimental effect on it's rankings
Well I believe that tables would be much more widely (and more readily) understood (rightly or wrongly) than the method Renniks posted for vertical centring.
Let me make it clear that 99% of my code is standards compliant and sans tables.
What I'm suggesting is that tables be used for less common tasks, like vertical centring and elastic equi-sized columns.