Always private
DuckDuckGo never tracks your searches.
Learn More
You can hide this reminder in Search Settings
All regions
Argentina
Australia
Austria
Belgium (fr)
Belgium (nl)
Brazil
Bulgaria
Canada (en)
Canada (fr)
Catalonia
Chile
China
Colombia
Croatia
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hong Kong
Hungary
Iceland
India (en)
Indonesia (en)
Ireland
Israel (en)
Italy
Japan
Korea
Latvia
Lithuania
Malaysia (en)
Mexico
Netherlands
New Zealand
Norway
Pakistan (en)
Peru
Philippines (en)
Poland
Portugal
Romania
Russia
Saudi Arabia
Singapore
Slovakia
Slovenia
South Africa
Spain (ca)
Spain (es)
Sweden
Switzerland (de)
Switzerland (fr)
Taiwan
Thailand (en)
Turkey
Ukraine
United Kingdom
US (English)
US (Spanish)
Vietnam (en)
Safe search: moderate
Strict
Moderate
Off
Any time
Any time
Past day
Past week
Past month
Past year
  1. rolandtanglao.com

    An Objective Look at Table Based vs. CSS Based Design. May 16, 2004. Finally. What Andy said! From Andy Budd::Blogography: An Objective Look at Table Based vs. CSS Based Design: QUOTE. Web standards and CSS based design are defiantly the way forward. However in our rush to advocate these "new" techniques, we may end up believing our own ...
  2. stackoverflow.com

    The short answer is that you should use tables for tabular data ( and not layout, see here why ), otherwise you use the right element for the right purpose, p for paragraphs, div for meaningful division ( don't abuse divs ), et cetera. Each element serves a purpose and you should use w3.org to look things up.. That being said, there are some people who still have the wrong frame of mind in CSS ...
  3. nickbradbury.com

    Andy Budd offers an objective look at table based vs. CSS based design, arguing that using tables for layout sometimes makes more sense than relying on CSS.He also states that the "CSS only" approach of some standards enthusiasts may alienate those not so well-versed in CSS. Although some of the purists in my customer base may be shocked to hear this, I'm inclined to agree with Andy.
  4. discusses the pros and cons when choosing between Tables or CSS Tables for your web pages. Examines factors such as bandwidth savings, load time, maintenance, conversion, W3C standards, R.O.I. (return on investment), 508 Accessibility, and learning curve and practical implementation. Sidebar: A close look at the CSS extremist and fanatic's arguments.
  5. 1.anagora.org

    layout: post title: Tables vs. CSS in Web Standards created: 1084776018 categories: Web Development In order to bring some balance back to the equation, and to have a bit of fun playing devils advocate, I've decided to write an article about why in some instances, traditional table based design can be as good, if not better than CSS and ...
  6. stackoverflow.com

    Yes if your application UI needs to be of high standards. No, if you are just learning to master some adhoc concept or coming up with a quick prototype. Benefits of CSS vs. Tables are well discussed. With CSS, a web site become more agile and accessible, have a look at CSSZen garden.
  7. webhostdesignpost.com

    There are some major differences when designing your layout to be used with Tables vs CSS. Most main factors are how flexible the design can be, how easy it is to maintain and the speed differences in render speed. Tables Render Slower than CSS. All web browsers have to render table code line by line before it can serve the content.
  8. Can’t find what you’re looking for?

    Help us improve DuckDuckGo searches with your feedback

  1. The short answer is that you should use tables for tabular data ( and not layout, see here why ), otherwise you use the right element for the right purpose, p for paragraphs, div for meaningful division ( don't abuse divs ), et cetera. Each element serves a purpose and you should use w3.org to look things up.

    That being said, there are some people who still have the wrong frame of mind in CSS, you should avoid layouts that are completely reliant upon absolute positioning and pixel perfect abuse, instead rely on fluid, em-based layouts when you can as these are more adaptable to different screen resolutions and environments.

    Other benefits of using proper semantically marked up HTML and CSS would be that you control all styles from the style-sheet, so that results in less tag soup code ( smaller file size ) and you only have to worry about updating content, not layout inside the markup [ separation of presentation ( css ) from behavior ( js ) and content ( html ) ].

    --meder omuraliev

    Was this helpful?
Custom date rangeX