![]() ![]() It's an illness, and IMHO it's just one step less evil than abusing tables for layout.Īny designer that insists to use loads of divs: AVOID THEM JUST AS WELL. Overdoing divs and spans has a name: "divitis". Sporadic use is of course still ok as we often have to render things that need something to contain something that's just too abstract to match any of the more semantically relevant tags. Why the past tense ? HTML5 is the way to go for new content, so you have many more appropriate options then to persist in splattering and all over the place. Prior to html5, you'd need something to use every so often to create more structure and then wasn't a bad choice. With html5, most often other tags are available and usable. , should be used only when no other tag is better - or can be used. you get it by now I guess.Īnd the layout is separated into CSS, outside and well separated from the HTML. about a financial document that compares the different source of revenue over the last 4 quarters or so): is the right tag.Ībusing tables for layout is 90's stuff: any designer that promotes that: AVOID THEM LIKE THE PLAGUE.įor lists. So for content that is tabular data (think e.g. IMHO the right answer is to use the right tag for the appropriate content. Just like headers are.Īnd we haven't even begun to touch on section, article, aside, etc. After all, like a div, it's another block level element. Lots of times, just leaving a paragraph sit alone is just fine. You don't always need a div to layout everything on a page. Now, one thing a lot of people forget, is that a div is just another generic container element. So, using tables for layout is for the lazy and those who don't know how to write proper markup and CSS and have no future in this business. Tables break that relationship.Īs an aside, the guy who first thought up the idea of using tables for layout, one year later in 1999(?), wrote an article called, "The Web is Ruined and I Ruined It". A properly laid out document looks like an outline you may have learned in school with headings and sections and paragraphs. They do not follow how a page looks on the screen but only the outline of the document. ![]() With all the devices out on the market today, tables are least able to accomodate them.ģ) Search engines can fail to understand the relationship from one table cell/column/row to another. Moving an element from one part of the page to another can be difficult to impossible, especially programmatically with javascript. which means they've never considered the poor guy who has to view your page on a mobile phone.Ģ) Tables are not flexible. Some may say, "Oh with the powerful computers we have today. The most significant are:ġ) Tables are slow. There is no reason to ever use tables for page layout. If you are not a beginner, are already competent at using tables for layout and want to build more pages and sites as quickly as you can, then continue with what you know. If you are doing it yourself and just a beginner, then you should learn to do it properly with divs. In answer to your question: i'd suggest that if you are employing someone to build your site, avoid anyone who wants to use tables for layout - the reason being it is more difficult to use div's and if they haven't mastered the use of div's correctly then i'd be worried about other holes in their knowledge. Technically div's are most likely to be the correct way to go, they also are much better to use if you are expecting your users to be using devices with very different screen sizes (assuming the site has been designed with this in mind) especially these days as most mobile devices have faster download speeds than an old time dial up connection (where every byte saved really counted)ĭiv's are suited for fluid designs, and many people use tables for an overall layout and also div's within the table cells. Google can tell what a page looks like whichever method you use and i don't believe there is an SEO advantage to using DIV's (not directly anyway)Īlthough lorax's point (2) is correct, the bytes you'd save by not using tables is trivial, especially if you have quite a few graphics on the page. Many people here will tell you that using tables for layout is wrong because it is semantically incorrect. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |