this is navigater div>
this is content div> div>
this is footer div> body> ... then define the style properties of each DIV in the CSS file. Obviously, the
tag named "main" is purely to control the "NaviGater" and "Content" two
layout. In this way, the HTML code of nested
is formed. The problem is that if you change the web layout in the future, you need to put the NaviGater in other places, such as "header". I am afraid that the CSS file must also modify the HTML file that refers to the nested
form. Because the nested
structure is actually written in HTML content for layout. In this way, the principle of "layout and content separation" advocated by XHTML CSS standards! I think, if the document structure is regarded as a logical structure that reflects the content, the document structure should be the logical framework of the content, reflecting the logical relationship between the various parts of the content, natively part of the content. The layout structure should be regarded as the physical structure of the content, reflecting the typesetting and display relationship between content. Document logic structures naturally have nesting, for example, "contact information" can be constructed by "telephone" and "email". However, it may often display the "phone" and "email" in different areas when expressing content. If, those
tags are completely nested according to the logical nest of the document, then "phone" and "email" will be very difficult to display in a
tab. The reason is that the nesting of the
tag is the layout structure, which is the physical structure of the expression. And the
tag is used to layout webpage. It is actually the most recommended layout of XHTML CSS. Moreover, in order to control the structure between the layout, the nesting
can be seen everywhere, some or the experience of the web design master. However, in fact, nesting
does tie the layout relationship with the content. However, there is no need to nested the
tag, I am afraid that only the method of absolute positioning and absolute dimensions in the CSS file can be defined in the location of the layout. However, this is a problem for those who need to come from adaptation and size according to content! From philosophical, XHTML CSS is unable to jump out of the layout and content of the content. It seems to be real "content" - "layout" - "Draft" separation, only use XML XSL CSS to do! But that is the final goal.
转载请注明原文地址:https://www.9cbs.com/read-75383.html
New Post(0)