| SitePoint Sponsor |




I don't understand your comment. The book that has been referred to in the recent posts in this thread is talking about using CSS tables for layout. There has been no change of opinion on anyone's part that the CSS should define the layout and that using tables in the HTML in order to specify the layout is therefore a bad idea.
By using tables in the CSS to define the layout to use for on the screen you can still use a totally different layout for those viewing the page from their mobile phone. You can't do that with <table> but you can with display:table
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">


C'mon people, don't feed the troll.![]()
Birnam wood is come to Dunsinane



The video and marketing are misleading. Besides they are trying to market the book. If anything using the techniques discussed within the book are more semantic because they allow one to cut down on wrapping elements due to anonymous creation. Still its probably going to be a while before I feel comfortable relying on some of those techniques.

There was similar marketing hype about Ajax a couple of years ago even though it had been supported by some browsers for 10 years. The marketing hype doesn't indicate a new product, it just indicates that someone wans to make some money out of an existing one.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">



Tables are not a design element. They are a container, just like a div.
A CSS layout involves Div(s)and/orTable(s)/CSS
That's what the video says.
That's what I've been trying to get into people's thick heads for a very long time
I know that's not what W3C thinks, but they're not the authority.
What works is the authority.


The W3C thinks correctly about the table element. Using the css table properties isn't spoken against by the W3C because it doesn't cause the same problems that the HTML tag does.
Programming Group Advisor
Reference: JavaScript, Quirksmode Validate: HTML Validation, JSLint
Car is to Carpet as Java is to JavaScript

The CSS table properties work fine in all modern browsers including IE8. It is only where you need to support old non-standard browsers such as IE6 and IE7 that you need to provide alternative CSS.
If you are coding XHTML rather than HTML you don't have a problem at all as all browsers that support XHTML also support the CSS table properties.
The W3C is the authority that those creating the browsers are supposed to follow in what their browsers can and can't do. Without that authority each browser would require its own proprietary code rather than all of them understanding most of what the W3C standard specifies. The W3C never has been the authority for people creating web pages except that since the browsers are supposed to follow the standards, following the same standards in your web page is a good place to start. Of course there are lots of standards you need for writing web pages that the W3C doesn't cover because their standards are aimed at the browser writers.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">
Your missing the point… the table tag isn't used. The display property for tables is inside the css. This forces elements that wouldn't normally behave like tables to behave like tables, but they aren't tables actually.Tables are not a design element. They are a container, just like a div.
A CSS layout involves Div(s)and/orTable(s)/CSS
That's what the video says.
That's what I've been trying to get into people's thick heads for a very long time
I know that's not what W3C thinks, but they're not the authority.
What works is the authority.
Bookmarks