A reflection on Web standards

Web|web Standard

I started learning Web standards from the beginning of last year, and I've had some experiences over the past two years. Recently job-hopping is just idle at home, write some out and communicate with you.

1 understanding of Web standards and the XHTML specification of the Consortium

By customary understanding, both concepts seem to refer to one thing (the "Advanced theory" ^_^ that we discuss in this edition). But I think, in fact, technically speaking, there is almost no correlation between these two things. The Web Standard in short is that the structure, performance and behavior of the page are independently implemented, more commonly speaking is now recruiting popular language "Div+css". However, none of the versions of the Web-standard XHTML is limited by any one version of it. Obviously, we can write a table-positioned page with XHTML 1.1. When I say this, I might think I'm talking a lot of crap. But any technology, only when you have a clear understanding of the basic concepts, you will use it correctly. Here are two ways to talk about the two misguided trends in Web Standard applications today:

The first situation is simple. I think that as long as the use of XHTML+CSS is the Web standard. The page is filled with class and ID. Arbitrarily define class for each detail. The difference between such a page and the traditional HTML is that the IMG tag has an extra "/". In fact, it's better to go back to the traditional HTML, at least I can use font easily, rather than always look up the style sheet like the dictionary. Another kind of more covert use of CSS I will speak in the future.

The second situation I find more difficult to understand, that is, trying to use a variety of complex div nesting and CSS statements to achieve the performance you want. A very simple example is just one of the posts I've just seen, "no Chettu page rounded corners." First of all I want to be sure that the idea is really good, using CSS features to "draw" the rounded corners. To do this, the designer must add a large paragraph of the following code in the appropriate location:

< /b>
< /b>

However, this is a serious violation of the basic concept of web standards-the separation of structure and performance. Because it places the code that controls the performance of the Web page in the structure document. You might say that it actually puts the real code of representation in CSS. But I think it's a concept of substitution. Because these B tags have nothing to do with the structure of the Web page, they are all empty tags. That is, it's not there to put something in the location that the document structure needs. So they're just some scrap code for the document structure.

Another example could be more covert. Before I have seen on the alistapart.com how to implement the Page three-way bar article, the principle is probably using three or four div nested each other. I think this is also a violation of the web standards of the idea of practice. Because these div tags are placed in the code is not simply for the structure of the need, but for the performance of the Web page.

Of course, I admit that the above views in a certain degree is a dead point (but, in turn, do not want to achieve a picture is not a rounded corner, hehe). Sometimes the structure and performance is not so easy to separate, we have to achieve some rich performance have to let the structure to accommodate (think of

Use). But it is important to know what is right and what is wrong. Even though we sometimes have to do something wrong.

Finally, I would like to state that I am not "not a picture fillet" is meaningless or wrong. I also admire the author's cleverness and inspiration. I think this kind of technical research is like the previous use of CSS painting the national flag, the CSS technology proficiency is very helpful. However, its use should only be as limited as the CSS flag, should not be adopted in practical applications. Because it violates the basic principles of web standards.