![]() ![]() 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. These benefits are not as noticeable when you first build your site, but any changes or even a complete redesign to be made later will be much easier.Many people here will tell you that using tables for layout is wrong because it is semantically incorrect. In addition, good semantic design (which means no TABLEs for layout) offers many benefits for maintainability and adaptability. DIVs are for page layout and TABLEs are for tabular data representation. Use them both and use them well.īottom line: each element has a clear purpose and should be used appropriately. DIVs are the correct technology for page layout and defining objects on the page (along with other block-level objects, i.e. TABLEs are the correct technology for tabular data. TABLEs for tabular data & DIVs for page layouts DIVs offer more flexibility and you can change the layout of the complete site by just changing a few things in the CSS file(s). CSS move the styling code off-page and into an external file, thereby keeping page sizes as minimal as possible. ![]() The use of DIV tags in combination with an external CSS creates smaller sized web pages which results in faster load times when compared to TABLE based layouts. Web developers started optimizing their web pages by applying web performance best practices, and also started avoiding TABLEs on their website and use DIVs instead. Last year after Google announced PageSpeed is going to be one of the factors for ranking in Google Search. Search engines look for content on the pages and not the HTML code for that matter, even the pages which are not HTML coded properly or W3C valid still get indexed and rank in search engines. Search engines and spiders don't care one way or another. A TABLE makes quick work for Tabular Data. To create something similar strictly using DIV tags would be very time consuming and would require a significant amount of code. ![]() Where TABLEs exceed is in displaying data such as Calendar or Price List (Tabular Data). DIV/CSS allows designers to change the entire look and feel of the website by only making changes to the external CSS file. Styled DIV tags are now considered the standard method for creating web design layouts by most web designers. Websites written using DIV/CSS are considered to be coded cleaner while nested TABLEs on the other hand can increase page size and weight. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |