I saw it yesterday in W3C that a new HTML5 draft (Working Draft) was released on June 10. I read the new version documentation it provides and took a little notes:
HTML5 draft has not become the official standardQuote:
Publication as a Working Draft does not imply endorsement by the W3C Membership.
Released as a draft does not mean that it has been endorsed (supported) from W3C members.
The HTML5 specification will not be considered finished before there are at least two complete implementations of the specification.
The HTML5 specification will not be announced until at least two software has been implemented.
XHTML1 was released in 1999 and it took two or three years to receive full support, and it was not until recently that it was fully promoted. So it will take some time to wait until HTML5 is supported (especially the non-mainstream browser). According to the timetable of the W3C's HTML Working Group, there will not be a formal finalization until 2010.
DOCTYPE statement that is surprisingly simple
<!doctype html>
It's that simple, ha. Moreover, there is no difference between upper and lower case. It is worth noting that the specification requires that if this DOCTYPE is declared, the so-called 'custom' HTML syntax can be used (custom HTML syntax, I don't know why it is called this), which is the previous HTML syntax that does not require tag closure. At the same time, it still allows XML format syntax such as XHTML, so that you must declare the DOCTYPE of the xml document without using the above.
Forward compatibilityThe HTML5 specification does not have deprecated elements because on the one hand, it requires designers not to try certain elements, but on the other hand, it requires browsers to support these elements. In this way, in my intuition, it is intended to support all previous pages written in HTML or XHTML. This is a blessing for designers, and they will no longer be restricted by the strict syntax of XHTML.
Deleted elementsOf course, these elements are relative to HTML4, but it can also be seen that HTML5 is not a simple retreat to HTML4. It still adheres to some important spirit of XHTML, such as pure interface expression elements should be abandoned and CSS is adopted.
Because their effect is purely presentational and therefore better handled by CSS, the following elements should be discarded:
basefont/big/center/font/s/strike/tt/u
The following elements are discarded because their usage affected usability and accessibility for the end user in a negative way:
frame/frameset/noframes
The following elements are discarded because they have not been used often, created confusion or can be handled by other elements:
acronym/applet/isindex/dir
What I want to explain here is: acronym is recommended to be replaced by abbr. But it seems that under IE, abbr is not as useful as acronym. For details, please refer to the HTML test document at http://www.mikkolee.com/3. Use object instead for applet. This label has long been abandoned. However, when I was studying HTML, I mentioned this applet in every book. At that time, everyone was full of longing for Java applets, but now they are sadly withdrawing from the stage of history, which is quite emotional. isindex and dir. I won’t talk about the two here, and I won’t recommend them when it comes to HTML3.
More new elementsHTML5 has launched many new elements, so I won’t list them here. Please see
http://www.ibm.com/developerworks/cn/xml/x-html5/.
If you are more interested in HTML5, there are some related articles listed at the bottom of this article, you can also check it out.
Original text: www.mikkolee.com/22