Historical issues of HTML and historical issues of HTML

Historical issues of HTML and historical issues of HTML

1.

<Style type = "text/css">

Once upon a time, HTML designers thought that there should be other styles in the future, but now we have realized that the facts show that, you can only use <style> without the type attribute (that is, type is optional). All browsers know that you are referring to CSS.

---- Head First HTML and CSS P29

 

2.

<Br>

The HTML5 specification clearly states that the use of elements should be based entirely on the semantics of elements. For the sake of ease, the standard also clearly states that for some elements, styles that are traditionally associated with them are also part of the semantics ......... However, many other elements have vague meanings, which are actually quite related to the rendering method and are contrary to the HTML5 standard goals.

---- HTML5 authoritative guide P126

Line feed labels are also a legacy issue in history, but this issue is not very big-because in HTML, different text structures are differentiated by line breaks, therefore, the effect of "line feed" is as mentioned in the HTML5 standard. style effects are part of the semantics. This is one of the reasons why the label is not canceled under the new standard.

 

3. Question about/in void.

4. Why is img an inline element?

According.

At present, many things do not understand. This pitfall is left empty first. Wait until I have mastered graph cutting, read the HTML5 authoritative guide, CSS authoritative guide, and work for about a year before I think about this issue. (Combined with articles in the bottleneck column in favorites)