11 ms·
Why CSS should not be used for layout
- windsurfer 18y agoFirst, http://shouldiusetablesforlayout.com/ http://shouldiusetablesforlayout.com/ for the idealist in me. Second, http://giveupandusetables.com/ http://giveupandusetables.com/ for practicality.
- burke 18y ago> http://shouldiusetablesforlayout.com/ http://shouldiusetablesforlayout.com/ Why do I still laugh every time I see one of these? I always see it coming...
- kajecounterhack 18y agoFirst, http://www.csszengarden.com http://www.csszengarden.com << for a reminder of why I might want to use CSS Second, http://www.nyt.com http://www.nyt.com << reminder of why CSS grids are so beautiful Then... a table on my site because I can't stand making two-column equal-height float hacks work anymore.
- josefresco 18y agoCSS layouts are a fascinating and sometime beautiful execution of technology, but it's not (at least this version) the next step in evolution of layout.
- dhimes 18y ago+1 for the second one. That made me laugh (and made me think that if I had something like this for all areas of my life I'd be single, have a 7th grade education and hoping the manager at Burger King returns my call...)
- mbreese 18y agoI particularly like that the first one uses a single table for layout. If you're reading the page's source, you'll also find this eternal wisdom: "Fact: Chuck Norris hates layout tables!"
- windsurfer 18y agoActually, if you check the first one again, it uses CSS, but it has a table layout commented out.
- moe 18y agoA well written and compelling argument. Way above the average CSS/Table rant for sure.
- markup 18y agoMay I suggest reading "Everything you know about CSS is wrong" by Rachel Andrew and Kevin Yank? It teaches to produce table-like grid layouts using CSS.
- axod 18y agoPlease paste a simple solution then using CSS, which behaves exactly like a table layout, and works in all browsers. I'm all ears...
- markup 18y agolinks does't support CSS, therefore "in all browsers" is a condition that can never be met.
- axod 18y agoOTOH, links supports tables pretty well. Regardless, a solution that works in IE6,7,8 Fx2,3 Op/Saf/Chr would be sufficient these days I think.
- markup 18y agoAs the book states one cannot provide such a solution for all of them. I get your (and other people in the favour of the table argument) POV, but I simply do not agree. I suggest people to read http://www.alistapart.com/articles/understandingprogressiveenhancement http://www.alistapart.com/articles/understandingprogressivee... and the other (most recent) ALA articles on the same subject from Aaron Gustafson.
- axod 18y ago
- alain94040 18y agoThe article's argument would carry more weight if the author gave an example using tables where he changes the order without affecting the layout. The whole point of the argument is to show that if you change the order with the CSS version, things move around. Then he goes on to show a static table. What the article really proves is that tables are not better than CSS. And CSS can do millions of things that tables can't (I'm not trying to start a troll on that topic). So I'll stick with CSS, thanks. There is one valid point in the argument: improving CSS so that you can position elements in relation to each other by name would help. So I could say that the DIV element called "left" should be on the left of the "center" element. Right now, relative order is based on the order in the HTML source.
- puns 18y agoThe strength of CSS layouts is flexibility. Yes, you need to fiddle a bit with it to make it all work, but the majority of the stuff is done in an external CSS file. Redesigning parts of a CSS site is much easier than with a table -- indeed it is almost impossible with a table in some cases because it is so static. With CSS you can change positioning and float it in another direction for example. A lot of repositioning can be done with absolute positioning, though floats are more ideal for the "core" structure. I think the example provided in the article is good though. CSS layouts should be so trivial to do, and it's a shame they're not. Going back to tables doesn't come without a cost however.
- bprater 18y agoMost sites also used a backend with their own templating functionality. Often, it's surprisingly simple for a programmer to change out the look of the site by tweaking a simple template.
- randallsquared 18y ago"What the article really proves is that tables are not better than CSS." Well, no. What the article shows is that, for layout, CSS has one of the same chief defects that people complained about for tables (content and presentation codependence), and that CSS doesn't even have the saving grace of allowing the content to be in the same order people read in (in Western languages, yes, yes), as tables do.
- nx 18y agoHe makes a great point. Besides, your tables will work on more browsers than the CSS layouts.
- deleted 18y ago[deleted]
- jneal 18y agoI'll stick with CSS. I've never once had to place CSS items out of order that is a ridiculous statement. There is a place for tables from time to time but once you actually "understand" CSS, life becomes much easier. I think the problem with most people is, they are told to use CSS, but without guidance they might not understand the core and basics.
- unalone 18y agoHis argument that you could take expert code and accidentally break it without much effort at all is a pretty sound one. I've designed a lot of stuff in CSS and I'm debating whether it's worth just putting it all in a table and getting it over with.
- bprater 18y agoExxxactly. If it takes an expert to do CSS, it may be an indication that it wasn't created well.
- Klonoar 18y agoI'm not sure what to think of your comment, to be honest. It's not an issue of how CSS was created that would cause the scenario (need to be an expert for CSS) that you indicated, rather it's how CSS ended up being implemented by the various browser vendors.
- Jem 18y agoAnd Lisp, Arc, Python, C++, C, ASP.Net Lua, etc... they don't require skill and expertise? Is that because they weren't created well?
- axod 18y agoPlease paste an update to the example, that just 'behaves' like the table then? eg the background goes to the bottom, bad things don't happen depending on size of the content etc. I've never seen a css example that behaves like a table.
- eli_s 18y agoI think it's pretty obvious that often tables are better and more intuitive to use for layout than CSS. The problem is that we've been told for so long that tables for layout are bad that it makes one feel kind of dirty using them. Web page layout should be simple it shouldn't require months/years of experience to work around CSS limitations and browser quirks to get some text and pretty pictures to display right. Sometimes I spend (waste) hours working on a CSS layout because it makes me feel clever, but lately I've been shrugging my shoulders, going the easier route, sending an invoice and moving on :)
- geuis 18y agoHis html example for the 3 column layout is subpar anyway. The wonderful advantage of CSS is that I can create a multi-column layout where the html might put the content div first and the nav last, if I have a reason to do so. My underlying html structure doesn't need to be in any particular order in order to achieve the layout that I want. He completely misses the fact that CSS2.1 has had display: options to do table-like alignment for years. These are well supported in modern browsers, except for IE6 and 7. I completely recognize this is an argument of "what should be" versus "what is". As it stands though, I have been doing this for years and have never, never EVER needed to use tables for layout purposes. I get that some people are more interested in writing applications and just don't have to time to learn all of the idiosyncrasies that go into dealing with cross-browser display problems. However most of these are easily overcome, most without even needing CSS hacks.
- eli_s 18y ago"He completely misses the fact that CSS2.1 has had display: options to do table-like alignment for years. These are well supported in modern browsers, except for IE6 and 7" haha are you serious? What percentage of people are using ie6 & 7? I think that layout shouldn't be that complex - lets be honest here we aren't building applications or anything difficult like that - we're layout out text and pretty pictures and CSS often makes this more difficult than it has to be. That being said I still use CSS as often as I can for layout.
- jonny_noog 18y agoI suspect he was serious, and he has a good point. If IE had supported "display: table" et al, coding CSS would be a hugely different and less confusing/frustrating experience for both the novice and the expert.
- eli 18y agoSure, and if it supported "display: hologram" we'd be able to surf the web in 3D. But it doesn't, and we can't
- deleted 18y ago[deleted]
- Klonoar 18y agoI'll tip my hat to the author for writing the first well-formed, non-ranting, description of why one should use Tables over CSS (that I've come across), though I'm sure with the amount of these people that are coming out of the woodwork I'm sure I'll end up seeing more... I still feel the need to disagree with him though. This kind of mentality is counter-productive to the web moving forward - CSS can be a bit more difficult at points, yes, but 90% of the issues that are generally encountered with it stem from IE's horrific rendering engine. We've finally gotten to a point where IE's market share is declining, and with that CSS based development will only get easier. On one last note, CSS is being adopted in more places than just the web - for instance, there's various projects attempting to integrate CSS into the GTK setup. If CSS was really that bad and unusable, do you think it'd be getting any further adoption at all?
- jrwoodruff 18y agoJust my two cents but I would say that this argument is not counter-productive, but rather essential to the web moving forward. Until CSS is improved, tables will never go away.
- Klonoar 18y agoI guess the way I'm looking at it is that this argument has already happened. CSS doesn't necessarily need to be improved, rather the browser situation does, which is certainly not helping CSS to look better in comparison to Tables. CSS3 (and CSS 2.1, which is still not fully supported in some cases) have various properties for forcing display models, but the caveat always ends up to be IE6/7. Though to be fair, I guess you're right, this argument is rather essential to the web moving forward, I just have to wonder if this is really the argument worth having.
- lsb 18y agoOkay, so why isn't "Center" centered? With the CSS, Top Center Bottom are all centered, but with the tables, they're not. Edit: am I wrong? Why am I being downvoted? I'm on Mac OS X 10.5 Safari 3.2.1
- irrelative 18y agoEven if they weren't, it's trivially easy to center it with CSS, or attributes. In the td tag, align="center", or in CSS text-align: center; Another pet peeve of mine with any CSS layout is that vertical alignment is a huge pain. With tables, you can use valign="top" in the td, or via CSS, vertical-align: top.
- drawkbox 18y agoIf CSS at this level of browser support isn't working for you then you are doing it wrong.
- bouncingsoul 18y agoIt doesn't matter if the logic behind using xhtml+css is flawed: the xhtml+css evangelists have so saturated the development world with their propaganda that I'm worried if I make an educated decision to use html 4.01 or occasional layout tables it will hurt me when potential employers, clients, or even the general webdev community review my code and think I don't know what I'm doing. Does anyone else feel that way?
- Klonoar 18y agoI always opt for HTML 4.01 Strict, just because the way XHTML is deployed on most sites is not actually XHTML, due to the mimetype that's being set. It really exists as badly malformed HTML. Furthermore, I wouldn't say it's propaganda. In a sense it's somewhat like the difference between functional programming and non-functional programming, i.e there's a difference there in the interest of maintainability.
- brianmckenzie 18y agoYes and No. It isn't just propaganda anymore. Pure CSS is what you're going to see in almost every code base you might work on. The last several gigs I've had wouldn't even allow tables for tabular data, which I think is ridiculous. If I were reviewing your code, I'd give you points for using tables to deal with tabular data. I might not even hold it against you if you used it in a layout, depending on context. Unfortunately the person reviewing your markup will probably expect pure CSS, even if it is data displayed in a table format. Adjust your expectations accordingly.
- eli_s 18y agoWow - not allowing tables for tabular data - this just shows how much kool-aid some people have drunk
- jcapote 18y agoHave fun seeing your SEO go down the drain. Also there are tons of CSS frameworks which do enforce layout semantics, possibly even better than tables ever could.
- motherwell 18y ago> Have fun seeing your SEO go down the drain. What rubbish are you reading? Tables vs css make zero difference. never has, likely never will, for all the obvious reasons (why bother? What difference does it make to users etc).
- dchest 18y agoI'm not a SEO expert, but I think the commenter referred to the fact that you can position content before navigation with CSS.
- pj 18y agoDo we really want this kind of bickering around here? There's a time and a place for every technology. Everything has pros and cons. There's no perfect solution. There are lots of good solutions. Sometimes CSS is one and sometimes Tables are one. Usually tables are used for tabular data. It is helpful for understanding what is on the page. It helps the robots. CSS knows nothing about the data. It doesn't care what's in whatever it is making pretty and the robots are fine with that. There's so much work to do. Why do we argue over these silly things. If you can do it with tables, do it with tables. If you can do it with CSS, I'll pay you 5 or maybe 10 dollars more per hour. Look, for every weakness you can find in the CSS route, I can find a weakness in the tables route. Try doing a fluid design with tables. Show me a search results page that will automatically fill in tiles to fit the users' resolutions. That's hard to do with tables, you have to use JavaScript and it's nuts. With CSS, just make them float left. That's why CSS is cool, little things like that. Yes, Tables are easier, they are. No one denies it. Easier does not make it better. Just because CSS has some flaws doesn't mean you shouldn't use it. CSS is good, it's separation of data and presentation. It's division of labor. It's not bad. It's good. If you have an application for example and you want to let your users put information anywhere using only one text file and without programming, let them do it with CSS. That makes sense. Tables are hard to make dynamic... Maybe that's the divide: static vs. dynamic Static layout with tables, fine. Dynamic layout with tables, not fine. Look, anyway, why all the animosity toward the CSS'ers? CSS is totally fine. No need to be hatin. It's not a popularity contest, it's a technology that can be used to do things.
- jimbokun 18y agoWho are you arguing with? Mr. Garrett states very clearly that both tables and CSS have a proper use.
- run4yourlives 18y agoI would be more inclined to be sympathetic to the cause of the author, and the ridiculous amount of people who upvoted this (wow, demographics change on HN, pg wasn't kidding) were he/she to show more than a three hour understanding of CSS. Obviously, when you can produce something like this: http://www.csszengarden.com/ http://www.csszengarden.com/, showing how a single html page can be manipulated in an infinite number of ways, it isn't CSS that's lacking, but your knowledge of it. I'm sorry if this isn't the popular opinion on this board, but as someone that coded tables and then made the transition, I can assure you that css is a much more powerful medium for web page layout, despite its quirks.
- wheels 18y ago> wow, demographics change on HN, pg wasn't kidding Right Click -> View Source
- bdr 18y agoI thought grandparent was referring more to the quality of the content than the claims of the argument.
- run4yourlives 18y agoI was thanks.
- DougBTX 18y agoAre there any examples in the css Zen Garden which have the really boring layout described in the article? Three columns which have the same height regardless of the height of the content in each column? If so, I'd love to see how they did it. The best way I know is to fake it using well designed background images. Quite painful to do.
- chairface 18y agoThe markup on CSS Zen Garden makes use of things like layers of wrapper divs to achieve what it does in terms of design. And this means the HTML is being used for more than just content, which is a direct controversion of CSS's goals. The site is actually a good example of what is wrong with the subset of CSS that is currently practical to use.
- Lucent 18y agoThe paradox is that CSS was not meant for precise layout. It was meant to only vaguely suggest a layout. That's why it deliberately excludes the ability to force elements next to each other the way tables can and spread them out evenly. It's not for generating pixel-perfect PDFs. It's for saying, "Hey, put some content here, make it kinda look like this, and if it doesn't fit, let it flow to the next line. No big deal." Yet the people who are so gung-ho about how it's superior to tables are...get ready: the people who think CSS is for controlling every pixel of a layout. Those people should really be using tables not because they're easier for what they want to do, but instead on principle! Instead we end up with some horrible, disgusting hybrid. Pixel counters for whom tables work perfectly instead abusing CSS to force a precise layout all the while gloating about how they're doing something noble and difficult and looking down their nose at those who do it the "easy way."
- olavk 18y agoI thing you got that backwards. CSS supports pixel-precise sizing and positioning. However, CSS also supports sizing and positioning based on the properties of the viewport, which adapt better to different screen sizes. Both approaches have advantages and drawbacks. HTML-tables OTOH does not support pixel-precize positioning, although you can get some of the way if you combine it with transparent gifs, as people used to do before CSS support became widespread.
- sh1mmer 18y agoThe author's point might have been better if there weren't a bunch of CSS libraries which have already solved this (http://developer.yahoo.com/yui/grids/ http://developer.yahoo.com/yui/grids/ and http://code.google.com/p/blueprintcss/ http://code.google.com/p/blueprintcss/ to pick two). You wouldn't rewrite cstdlib why would you rewrite your CSS framework for every project? More over I think a lot of people neglect the real issue which is the high touch point of the Web, it's the multiple clients. You try to write cross-OS GUIs in Java and Swing and find out how easy that is (it isn't, obviously). The reason people advocate CSS is that it presents some real tangible benefits. CSS was specifically designed to present the semantics of layout rather than HTML tables. The author doesn't even talk about CSS tables (http://thinkvitamin.com/design/css/tables-the-next-evolution-in-css-layout/ http://thinkvitamin.com/design/css/tables-the-next-evolution...). Again I wish people would talk about technologies they were familiar with and had even made spent time with. You don't see me critiquing the algorithmic design of search engines because I didn't choose to follow CS down that route of expertise.
- Spyckie 18y agoGrids need more coverage, as they are by far the best way to bypass css misery and create a flexible, controllable layout for your website. They require a whole lot less markup than tables, are more intuitive, are much more controllable, and in general should never be not used. With Grids, you start thinking about ratios rather than pixels, which is a real help in making your site aesthetically pleasing and flexible.
- psadauskas 18y agoYeah, pretty much. I'm not sure why this debate is even still coming up; It's been "solved" by a half-dozen grid frameworks. The other issue is that people trying to get these pixel-perfect layouts need to rethink their strategy. Its a hypermedia document, stop trying to make it look like a printed page or a magazine ad.
- jrockway 18y agoI agree with this guy -- CSS is horrible :) One of my Great Plans For The Future is to write a language that abstracts away HTML, CSS, and (some) JavaScipt. You describe your layout in a format that makes sense, and the compiler will decide whether to use tables, CSS hacks, or whatever. Ideally, this wouldn't be necessary, but I've never written CSS without the knowledge of the HTML it's going to be applied to, nor have I written HTML without considering how to style it. I am not being dumb, either. HTML needs all sorts of hooks for styles (classes), since HTML doesn't have any meaningful elements. (Oh boy, I get <p>, <strong>, and lists.) When I have done three-column layouts, my HTML has always needed tweaking -- the content has to be in a certain order (usually left/right/center, which is stupid), and it has needed hacks like <br class="clearfix">. So clearly we don't live in an ideal world; we are stuck with HTML and CSS the way they are. It is time to abstract away the stupidity like programmers abstract away the computer with high-level languages.
- ars 18y agoWhen you first start learning CSS you learn how to get rid of tables. When you get really good at CSS you learn when to bring them back.
- bravesirrobin 18y agoOne thing that CSS does especially badly that tables do well is correlated sizing. It's easy with tables to make all the elements in a layout row all have the same height. Doing the same in CSS is possible but requires so many hacks that the net result makes you feel dirty. I've watched this war for years now, and just wish both sides would give some ground. As long as you do your layout with the fewest amount of tables needed (trending toward zero), the you shouldn't need to guilt yourself out about it.
- tripngroove 18y agoI have the sneaking suspicion that there are a lot of coders contributing to this recent rash of CSS vs. table discussions who flat-out don't know how to write CSS very well, and can't be bothered to learn. That was my obligatory quasi-offensive hook to get you reading. Now, before you actually get angry... there's nothing wrong with that! You're a coder! Do what you do best - write awesome useful stuff! ...and don't be afraid to acknowledge that there's a language out there that looks like code, but that you don't have a handle on. As someone who has spent the last several years doing nothing but writing HTML and CSS in a professional capacity, I am here to tell you that if all you beautiful, intelligent hackers out there (I'm only being facetious about the beautiful part, 'cause I've seen some of you ;) really understood front-end layout the way you understand all your programmy stuff (which I do NOT), we wouldn't be having this discussion. If you're just working on a personal project, or trying to hammer out the beta version of your web app... sure, use tables, so you're not wasting time trying to do something that's not your core competency. However, if you're taking it beyond that, or trying to get into front-end stuff in a professional capacity, you need know CSS like the back of your hand. Someone who's competent at layout should be able to write something from scratch that does whatever they want it to without having to debug it for hours. If you're at the point where your biggest problems would be solved by using table layout instead of CSS, you're probably not at a point on the CSS learning curve where it's appropriate to make assertions about which layout technique is superior. All that said, if you're a coder, why do you want to get into layout anyway? Your skills are WAY more valuable... designers like me are just here to make your work look good ;)
- josefresco 18y agoI'm not a coder (pro designer for 9 years) and usually back most arguments made for Tables. Sure CSS is slightly more evolved but sometimes using older tech makes much more sense for other reasons (besides content vs layout). Also support for Table layouts is still strong and there's no compelling reason to upgrade for most webmasters. However I'll agree with your assessment about coders being too lazy to learn proper HTML. ducks
- daleharvey 18y agoI dont want to speak for everyone at least but I dont particularly agree with thin divide between programmers and designers, the lack of gap is one of the reasons that the web is so popular. While I havent seen that many programmers who can produce aesthetically brilliant design, I have seen far less designers that know nearly as much about the technical limitations of css layouts as the typical web programmer. There are solid situations where css (as much as I love it) just isnt capable and isnt the best solution, it isnt just down to lack of knowledge.
- tripngroove 18y agoThis is going to sound totally flippant, but I think it's always worth considering sources... let's take a look at the author's site, and reflect on how we feel about taking front-end design advice from this person.
- jacquesm 18y agoI agree, so I read a bit further after looking at the page (which is, conceded, not exactly a high point in design), here is an interesting bit of information about the author: http://sitereservation.com/xooglers/index.cfm?entryid=16 http://sitereservation.com/xooglers/index.cfm?entryid=16
- GHFigs 18y agoI find his choice of "typical" CSS layout to be misleading, when neither his site (which uses CSS, naturally), his blog (CSS), any of the pages he links to (CSS), or this site (tables) use such a layout. Yes, he chose it to illustrate his point, but that point doesn't connect to the trollish overstatement of the title. It is evident that person can use CSS for other layouts (even using floats) without ever encountering the problems he describes. The real conclusion here is that CSS is hard or even impossible for some desired layouts--something just as true with tables. I doubt that that's news to anybody.
- chairface 18y agoThe auto-expanding equal height three column layout is such a standard layout on the web, and ways to do it are so often requested that it is referred to as the "holy grail" by the CSS community. So I find your critique and accusation of trolling to be rather misplaced.
- GHFigs 18y agoI did not say it was uncommon, I said his choice was misleading. It's a trick: it allows him to demonstrate a problem with one kind of layout using floats (which by definition do not behave like tables) but then claim it is generally applicable to all layouts and CSS in general. It is not. I stand by my statement that his title is a "trollish overstatement". It was chosen for the sake of continuing argument, not reflecting the content, educating, or informing.
- chairface 18y agoYou said it was misleading that he implied it was "typical", which is a synonym for "common". You can take issue with his conclusions, but illustrating your thesis with a common case can in no way be construed as a trick.
- GHFigs 18y agoYou're missing the point. Yes, it's a common case in that it occurs frequently, but it is not a typical case in that it is characteristic of the whole set. That is my problem with it, as stated for the third time. His conclusion reaches far beyond what his carefully selected evidence supports.
- olavk 18y agoThis whole CSS vs. HTML-Tables discussion is ridiculous. It is not either/or. There are some specific cases where Tables are superior over CSS, but many things can be done with CSS which is impossible to achieve with tables. This article explanin the concrete cases where you should use tables: http://olav.dk/articles/tables.html http://olav.dk/articles/tables.html The submission shows some examples where tables are needed. However, one could easily show other layouts where HTML-tables would be useless and CSS is necessary. Any serious web developer need to know the limitations of both tools. BTW. the submission also contains some major misunderstandings: > when it comes to layout, the design of CSS is fundamentally flawed. Use tables instead This is blaming the shortcomings of Internet Explorer on the design of CSS. The CSS spec supports exactly the same layout model as HTML-tables, it's just that IE doesnt support this CSS feature.
- iroboto 18y agoThe arguments presented seem like a half truth to me. 1 HTML multiple CSS not 1 CSS multiple HTML The whole concept should be that HTML should be written to have 100% accessibility across all readers (browsers and mobile devices), meaning someone with the most ancient browser can read the page and understand the content of everything without any form of presentation. What the author has done essentially is the following: Try reversing some words in a sentence and then later complain that English is flawed because the sentence no longer makes sense reading it left to right. The HTML won't make any sense if you start reversing it... I mean what is the point of putting <h2> tags below your <p> when it's obvious that the <h2> tag is acting as the heading for the <p> below. I wouldn't be able to read that, so why is CSS @ fault? The logical flow of the content should be based upon the reading the raw HTML in a procedural order. This will keep it simple for coders to update the content, and css artists can pump many different layouts and show many different layouts to clients in a matter of seconds. Good CSS also requires good HTML. Why the author of the article is using a div container to wrap them all when a body tag exists is beyond me. I think as much as we point our fingers at css as a flawed language, we need to point our fingers at how write our HTML as well. www.csszengarden.com
- chairface 18y ago> I mean what is the point of putting <h2> tags below your <p> when it's obvious that the <h2> tag is acting as the heading for the <p> below. I wouldn't be able to read that, so why is CSS @ fault? Nobody is talking about putting headers after the content they're introducing. The author is talking about a situation where it makes sense to order the markup one way, but CSS demands it to be done a different, not easily readable way. Which does happen sometimes. > Why the author of the article is using a div container to wrap them all when a body tag exists is beyond me. This looks like a ridiculous statement to me. But please, explain further what you want him to do. I find it comical that you go on about "good HTML" and then point to CSS Zen Garden, where the HTML is inextricably bound up with the presentation (ie, adding wrapper elements to allow for flexibility in styling). CSS Zen Garden is an example of HTML as it should not have to be.
- iroboto 18y ago
- wooby 18y agoA related argument against table-based layouts, which I don't see any discussion about yet, is that "it's important to maintain a high ratio of content to markup for SEO purposes." In my view, a complicated div-based layout is just about as markup-heavy as a table layout, given separate CSS files in both cases. So I would think the point is moot. And my suspicion is it's just SEO firms blowing smoke in an effort to figure out things to sell. So, is this at all a substantiative claim?
- rgrieselhuber 18y agoI still don't get this debate. Before, it definitely used to be easier to just use tables, but now there are so many examples and frameworks out there that I never spend more than 20 minutes or so with CSS, even on very complex layouts. What am I missing?
- jacquesm 18y agoOne of the most compelling arguments for css is to use it rearrange the content of your webpage so the most relevant content appears earlier in the data. Apparently this can have a significant effect on your search engine optimization.
- euccastro 18y agoIf it's your choice, making the most relevant content appear earlier in the layout too (thus removing the need to reorder) sounds like a good idea.
- knieveltech 18y agoFail.
- nw 18y agoConceptually, styles and positioning are two different animals. We need a tripartite model of 1) content, 2) styles, and 3) layout/positioning. Unfortunately neither tables nor CSS handle positioning well in all cases, hence the perpetual argument. Maybe I'm just ignorant, but I've found it necessary to use CSS, tables, & JavaScript (yes, all three) to produce acceptable dynamic layouts for web-based apps. This is unfortunate.
- dezwald 18y agoi hope this comment speaks for most. In a perfect world, CSS is awesome. tables are good, except when it comes to a point when you have to start nesting tables within each other to format your your layout. explanation is below: --------------------------- people who love tables would switch over to CSS if it did what everyone(and standards) makes it out to be and actually worked and/or rendered the same in ALL browsers (css hacks don't count as css) but no matter what you say about CSS....(and i'm all for CSS) ...CSS can't solve all design issues...and if it can...it takes way to long to figure out... and if only a 10 year veteran/css master can implement flawless layouts then CSS isn't a practical language. in theory is CSS is awesome! i use tables for tables (tabular data) and i use CSS to layouts and comesic design. think about it...if CSS rendered the same way in every browser abiding by CSS standards ...even developers who are pro tables...would switch over. the reason why there is such conflict between tables and CSS is because many of people have tried CSS countless number of times and hours trying to make their template/layout work...however they've came across so many road blocks ...they give up. i'm not saying tables are the ultimate design language...and i think people agree....they just use it because it works. in ALL browers! but me say ONE LAST THING! its not CSS the language that is problem....is the number of browsers that choose not to render CSS properly.