Talk:Tableless web design

message: I created and have been maintaining Holy Grail (web design). With the growing acceptance of CSS3, that page is becoming of less practical value, and will someday have only historical significance. So the time is approaching when any worthwhile content should be merged with other articles, and the original article then proposed for deletion.
Holy Grail is a subset of tableless design. So this article is a likely candidate.
My opinion is thus:
* There should be an article titled "Web Page Layout", with general and uncomprehensive coverage of the topic.
* Tableless, Responsive web design, Framing_(World_Wide_Web), and perhaps other articles should be largely merged into the new article.
* The more specific articles might remain with more specific content.
* Holy Grail should be merged with the new article, and tableless.
* This would be a major undertaking that should be started in User Space.
* It would be helpful to prepare an outline which organizes what would appear in which article.
What say ye?  — Preceding unsigned comment added by Davidlark (talk • contribs) 02:41, 8 September 2017 (UTC)
thread_title: Proposal: Integrate other page content

message: Where is the criticism that CSS is horrible, because you cannot resize the font in the browser without it going out of whack?   —Preceding unsigned comment added by 75.200.157.78 (talk) 03:07, 21 April 2009 (UTC)
thread_title: Criticism:  Where is it?

message: I believe that this page could be improved by changing its focus from an argument for CSS to a historical perspective on why people used tables for design, and the difficulties transitioning from tables. The page should be targetted to people who came across the term "tableless design" and wonder what it means. The structure I propose is: 
The first section should describe why people used tables for page layout. This should be written in the past tense.
The second section introduce replacement technologies (with release dates and links to other pages). 
The third section should describe historical difficulties of transitioning to CSS (for example, Netscape 4 did not adequately support CSS, and there was not a clear upgrade path for Netscape 4.) 
The problem section should be about current thoughts on the term. e.g., this is an antiquated term that only has meaning for people who are using tables for page layout and need to change to CSS. These changes would make the page more interesting and relevant to the casual reader. Yintercept 19:09, 8 April 2007 (UTC)
replies: text: I put together some historical remarks: The Tableless Table - Armin B. Wagner (talk) 12:49, 8 May 2009 (UTC)
thread_title: Propsosal: Change to historical perspective

message: I've tidied up this article and expanded it a bit. One thing that I thought about including but wasn't entirely sure about was the advantage of tableless web design as far as Search Engine Optimization is concerned. I gather that having a table-less design that is valid (X)HTML does have a beneficial effect on search engine rankings though I'm not 100% sure about this. Perhaps someone more knowledgeable than me about this aspect of SEO could add some appropriate blurb if it is relevant? Jammycakes 22:19, 19 April 2006 (UTC)
replies: text: Really this is just one element of semantic HTML, which in turn is a part of standards-based web authoring.  See talk:Tag_soup#Citations and Neologism. —Michael Z. 2006-10-16 05:59 Z
There is a lot of speculation about Tableless design and SEO. I've heard some ridiculous claims. From a search engine's perspective: It is not important how a web designer codes a page rather the content on the page. It could be considered unethical to penalize a web page because it used a certain tag.
In extreme cases excessive tables will impact on search engine rankings but this not due to tables but poor HTML. Any tag will have the same effect if used too much. Rimian  —Preceding comment was added at 11:06, 13 December 2007 (UTC)
thread_title: tidying up page

message: The CSS file can also be cached by the browser and so does not need to be re-loaded with every page visit, thereby providing further savings in bandwidth.
Aren't images and HTML also cached? How is this an advantage of tableless web design? I'm not sure I understand what the author is getting at here.
CSS is cached across multiple pages. HTML is separate for each page.  Pretty straightforward, I'd say
: I've reworded it a bit to make it clearer. Jammycakes 07:00, 16 May 2006 (UTC)
thread_title: css cacheing advantages?

message: Why are there purported disadvantages listed in the "Advantages" section?  Move them to the "Problems" section!  Specifically, see the second and third paragraphs under "Bandwidth Savings" as well as the fourth paragraph and second half of the third paragraph under "Maintainability". 
REggert (talk) 16:42, 15 April 2008 (UTC)
replies: text: I'd suggest not having advantages and disadvantages sections.  I thought for&against sections were discouraged because they lead to multiple discussions of the same topic. For example, bandwidth savings would end up being split in two pieces: "clever use of CSS can result in bandwidth savings" in the advantage section and "complex or misused CSS may result in higher bandwidth usage" in the disadvantage section.  Maybe advantages and disadvantages could be combined into "Considerations" or something similar. --216.62.101.13 (talk) 20:00, 17 April 2008 (UTC)
thread_title:  Are they advantages or not? 

message: This article is basically a POV essay. It makes some bold claims and cites very little. The section on bandwidth savings totally ignores the fact that you can use HTTP to send compressed HTML. What a bunch of baloney. 66.117.135.137 (talk) 04:41, 4 May 2008 (UTC)
thread_title:  This article is BUNK 

message: The grid systems of these Renaissance artists was used to create a sense of depth and 3D perspective on a two dimensional surface. This has nothing to do with typographic grids, which are a development in modernist typography. Bangpound (talk) 01:50, 4 February 2009 (UTC)
thread_title:  Brunelleschi and Masaccio? 

message: "As of 2006, CSS layout capabilities improved considerably."
What happened in 2006? Ojcookies (talk) 05:06, 17 April 2009 (UTC)
replies: text: IE7 was released in 2006, as was Firefox 2. I don't know whether either of those were the reason it said 2006, though. Someone's changed it to 2009 now. xx521xx (talk) 23:15, 7 September 2009 (UTC)
thread_title:  Quick point 

message: Unfortunately, "tableless web design" is often a "religious argument" thing. CSS "gurus" write books to enlighten us "sinners" about the "better" way of doing things, and condemn the "evil" of using tables for layout. The "experts" make various theoretical arguments about the advantages of CSS for layout, while the downsides and pitfalls are mostly ignored. Meanwhile, tables function just fine in the real world, are reliable, automatically adjust to different browser sizes, and are intuitively obvious to anyone familiar with HTML. If someone prefers to use CSS for layout, that is fine with me. 71.217.14.36 (talk) 07:24, 1 July 2009 (UTC)
replies: text: I'm surprised to see the W3C's advice dismissed as religious zealotry. And I guess blind readers, those viewing the pages on mobile phones, and automated acquisition (by bots, for mashups, etc) can just go hang? --Nigelj (talk) 22:31, 19 February 2010 (UTC)

text: I agree that the article is written in a largely POV perspective (that CSS is good, tables bad...).  Nigelj's response is a prime example of the "zealotry" he tries to dismiss, by blatent condescension.  My mother is blind, and has absolutely no trouble "reading" (using a screen reader) or understanding any web page, regardless of layout method.  And, actually, the only problem she may have is style based - that is, a poor page style regardless of the underlying html/css. --70.126.46.188 (talk) 14:24, 8 June 2011 (UTC)
thread_title:  Too much "religious" argument 

message: I'm not a code boffin, so correct me if I am wrong, but there appears to be at least one table being used in the source code of the Wikipedia page called "Tableless Web Design" (and on this 'discussion' page too) Also, Google, and Walmart, BBC, Amazon.com, some of the biggest websites in the world, still use some tables on every page in 2010
:On WP, do you mean the 'Table of contents'? The clue is in the name. This type of correct use of a table is covered in the article. --Nigelj (talk) 12:46, 5 June 2010 (UTC)
replies: text: Although, I have to say that the following (in WP's markup) looks 'sub-optimal':

 
  Contents
 
We could have:
Contents
--Nigelj (talk) 12:56, 5 June 2010 (UTC)
thread_title:  Tables still being used 

message: Example images showing tabled and tableless design would be helpful to aid the non-expert reader. Crookesmoor (talk) 10:44, 22 November 2013 (UTC)
thread_title:  Images 

message: Omits to mention the two greatest detractors of div-based page design:
: Excessively long or oversized text in a div-based container tends to 'bust out' of its container to overlap other text or graphics, making the page completely unreadable. Table-based layout generally does not suffer this problem because table cells resize gracefully to accommodate their content.
: Left or right-positioned columns using divs must use the float: attribute, and this has the undesirable side effect of making the vertical positioning of the container indeterminate, such that on some screen sizes it may appear above or below other content instead of alongside. By contrast a table row is a table row, and cannot become a column, or vice versa. 
In css3 the ability to make divs behave like table cells was added in response to these criticisms, but doing so requires extremely verbose and untidy code. Hence it is not a very satisfactory response to the problem.   
In short, this is really an argument between theorists hard-selling a flawed ideal, and the real world in which we use the method that works reliably. 
The article also gives the impression that css layout control cannot be applied to tables, which is completely untrue. The outdated practice of positioning content by the use of spacer images is completely irrelevant to this subject. --Anteaus (talk) 09:47, 2 July 2015 (UTC)
thread_title:  Poor handling of overflow by divs, main reason for using tables.   

message: Hello fellow Wikipedians,
I have just modified  on Tableless web design. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive http://web.archive.org/web/20090216193839/http://www.chromaticsites.com:80/blog/13-reasons-why-css-is-superior-to-tables-in-website-design/ to http://www.chromaticsites.com/blog/13-reasons-why-css-is-superior-to-tables-in-website-design/
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 21:15, 25 May 2016 (UTC)
thread_title:  External links modified