This way, you can understand what is considered valid in HTML5: That’s a fairly comprehensive, though hardly exhaustive, list of differences between XHTML strict and HTML5 validation.
Some are style choices, so you’re encouraged to choose a style and be consistent.
The specifications will always contain the most up-to-date information.
In the next chapter, we’ll look at a crucial segment of new functionality introduced in HTML5: forms and form-related features.
), the specs can provide a more complete picture of how a given element is intended to be used.
Remember that the HTML5 specification is still in development, so some of what we’ve covered is still subject to change in the new HTML5.1 version (or in the HTML5 “living standard,” if you go by the WHATWG’s definition).
If you’re unsure about how an element is meant to be used, go back and read the section about it, or better yet, read the specification itself.
He blogs at Impressive Webs and curates Web Tools Weekly, a newsletter for front-end developers primarily focused on tools.In the previous chapter, we introduced you to a number of syntax changes in HTML5, and touched on some issues related to validation.Let’s expand upon those concepts a little more so that you can better understand how validating pages has changed.The best way to become familiar with HTML5 is to use it—start with your next project.Try using some of the structural elements we covered in the last chapter, or some of the text-level semantics we saw in this chapter.