Several years back I suggested a GRID element that could be used for
presentational, layout purposes to obviate the need for hijacking the
TABLE element for something it wasn't made for. It was on this very list
but was considered to be an HTML subject, not a CSS one, so I was asked
not to discuss it here anymore.
The "tables for layout" issue has caused untold grief in 13 years of web
development for me. I didn't even start out using tables to lay out the
websites I created but when I got my first professional job in the field
I was told I should use them. So I did. Then I began transitioning to
using CSS for layout but continued to use tables for their proper
purpose: presenting tabular data. But then I encountered prospective
employers who had heard the mantra "don't use tables for layout" but
misheard it as "don't use tables for /anything/" who told me they
couldn't hire me because they found TABLE elements in my markup in sites
in my portfolio. Now the HTML Working Group says, "Yeah, go ahead and
use tables for presentational purposes." Ugh. Can't win for losing.
Christian Z.
P.S. We shouldn't complain about Google throwing their weight around
when we as a society have erroneously acted like theirs is the only
search engine that could ever yield legitimate results.
*** Decision of the Working Group ***
Therefore, the HTML Working Group hereby adopts the "Allow tables to be
used for presentational purposes" Proposal for ISSUE-130. Of the Change
Proposals before us, this one has drawn the weaker objections.
______________________________________________________________________
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/