Table history
Before the tables came, the web was a useless place. Using layout tables has opened up new ideas for “design” page opportunities. It can be argued that the table-based structure was responsible for the popularity of the web and the web design sector.
Worse, over the past few years, the table-based structure has been widely criticized and demon-possessed. Webmasters say that tables are never made for design and should not be used for that purpose. The rapidly evolving hype is reflected in the air all around.
The truth behind the hype
Despite the fact that pioneers have long talked about web standards, most websites are still developing using tables and code that do not conform to standards.
History has shown many examples of technology that began with a single purpose, and they eventually discovered some useful properties that could be used as alternatives. And it sounds very appropriate in the case of tables. The web itself is not intended to be a channel for teaching, marketing and information but for sharing research data.
Using tables is a pragmatic method, if not selected
The W3c Web Access Guidelines recognize that designers will continue to use the layout table - so they incorporate information on how to use it in the most accessible way. Designers will not immediately stop using make-up tables; especially the ownership of the reason why this is the default behavior of most WYSWYG (what you see is what you find) Web design packages and; Structured CSS is very difficult to use successfully.
In addition, Experts still oppose the use of table layout tables on the web, despite the fact that this is against current standards. They argue that it is a pragmatic approach - if not their choice.
Let's explode legends: CSS vs Tables
Most web designers just don't feel the need to change
Many websites are still developing using non-standard tables and codes. As a result, user agents will be forced to manage table-based properties for many years to come. This successfully dumps one of the major web rankings. That's a forward move. As a result, many web designers really feel the need to start developing sites using CSS-based formats and code-compliant code.
CSS development has a much higher barrier to entry than table-based design
While comparing table-based layouts with CSS-based design, the CSS syntax, of course, turns out to be very simple. No one with the right mind can argue that you too need to be a rocket scientist to learn CSS. However, some ideas may be more difficult to integrate.
Continuing in the same spirit it is true that there are many bugs, even “experts” find themselves spending a lot of time fixing bugs. For the novice this should be very frustrating. We do not know if the problem lies in your misunderstanding of CSS or an obscure browser bug.
Perhaps that is why so many people view web rankings as “Ivory Tower” and why so many webmasters are coming up with a sense of accomplishment and a passion for web design.
Some things are easier to do with tables
People often find themselves writing complex CSS to do something that can be trivial using tables. Take form style as an example. It is possible to place very deceptive forms using tables in just a few minutes. You can achieve the same results with floating objects with CSS, but it is more involved. If you are a CSS reader it is all part of the fun. However, if you are a mortal, it can be incredibly frustrating.
One such thing is on the feet of the page. It is very easy to do using tables. While you do this using CSS alone, it would not be surprising why web developers turn their backs on CSS when even simple things are done.
If you have the knowledge and patience, you can do many things using the CSS you usually do using tables. Sure it may take you a long time, but you will get there in the end (or die trying).
Benefits of CSS. But does it give you what you need?
It is true that changing a large site in a CSS-based layout can save a huge amount of bandwidth. However, for many sites, this save will be insignificant or even insignificant.
People are looking for quick download pages and many attorneys have suggested that CSS help achieve this. At most sites, the "design" is evenly distributed throughout the site. However with CSS-based sites, “design” is usually captured in one or more external files. These files can be complex, and even on a simple site, they can be large, or fast.
Search engine friendly: CSS vs Tables
It is true that search engines like semantic pages. There is also the widely held view that search engines such as soft code. Creating a site using CSS and web rankings can scornly promote the development of sites that are relevant to search engines. However it is not a magic bullet, or a panacea either.
There are many table-based sites that earn the highest scores on search engines. It is equally possible to build a CSS-based site that detects bad search engine rankings. The most important thing about high quality content and inbound links, not that the site uses tables or CSS layout.
Accessibility issues
An increasing number of people are trying to sell web rankings and especially a CSS-based design by playing for fear of client accessibility.
There is nothing naturally inaccessible about a table-based structure. While it is true that your site needs to be published in a well-known grammatical set to obtain AA accessibility rating, table layout is only a recommendation, not a strict AAA rating requirement.
The last word
Final Table based design will be available for a long time. However, it is wrong to say that it is wrong to use them.
You must be logged in to post a comment.