When will you start using HTML 5?

Question

So, HTML 5 is widely known, and is expected to be ready by 2022 . It's a long wait, and the test for this readiness is that "at least two browsers completely skip [HTML 5 test packages]"

Obviously, in order for browsers to pass this test, before that they must begin to implement the HTML 5 functions used. The list of new supported HTML5 functions looks thin at the moment. But there are a couple of significant changes to existing elements , such as the possibility of A tags, to the level of the surrounding block, which can be very useful now.

There are sites that use HTML 5 now , so what factors make you start or keep you from building sites with HTML 5 doctype?

I myself, I play with HTML5 on several personal sites, but I will wait for time on working sites until things like a reliable validator appear.

Answer 1

This helps to split this question into several parts.

1) When do you need to start using HTML5 doctype?

An HTML5 document forces browsers to display pages in Full Standards mode. If you are not currently using strict doctype, pages may display differently. Therefore, you need to weigh the required refinement if you are converting an existing site, and you need to understand the difference in behavior. Secondly , doctype will cause the w3c validator to choose HTML5 as the default language for validation. Given that HTML5 is still a draft , this means focusing on a moving target. Is importance important to you? Some features that are valid in HTML4 are not currently valid in HTML5. If you change your markup now to remove these features, given that HTML5 can change to enable these features again? If you like it, you can start using the HTML5 doctrine.

On the other hand, in fact, what are you gaining? If you want browsers to display in Full Standards mode, you can use strict doctype from HTML 4.01 or XHTML 1.x. Do you need HTML5 validation given that it will convey things that currently cannot be processed sequentially in browsers? Keep in mind that any HTML5 feature that currently works in browsers works whether you use the HTML5 method or not.

2) When should you start using features that are currently functionally implemented in major browsers but standardized for the first time in HTML5?

You can use them now, but try to make sure your pages are properly accessible. For example, Canvas does not provide good support for unsuspected users.

3) When do you need to start using the features that are currently implemented in some browsers, and will HTML5 be standardized?

It depends on your target users and delivery schedules. Will your users use a browser that supports these features by the time your site begins to live? What happens if they do not? Does the page recede gracefully? You do not like if some users can not use your site?

4) When do you need to start using HTML5 features that are not yet implemented?

Why do you need this? This may be reasonable for training purposes or for researching return behavior, but HTML5 is still a draft, and it is possible that some features will never be implemented or will be implemented completely differently as described at this time, therefore you could spend a lot of effort.

To summarize , it’s important not so much in the HTML5 project as in what you can practically use today. The project describes a number of functions, some of which have been in browsers for many years, some of which are new but have support or good return behavior, as well as some that are currently not available and may never be used.

For me, I will hold on until I need the HTML5 function, and I know that this function is implemented in a consistent and stable way in major browsers. This is likely to happen during the HTML5 Last Call phase, or perhaps during the candidate recommendation phase.

Answer 2

Already started using it for personal and client work.

For verification I use Henri Sivonen excellent http://validator.nu/

Answer 3

When IE supports it. I work in the corporate world and IE is required.

Answer 4

I am using doctype now! (at least for some projects)

In terms of features, things like <canvas> and <video> are cool and useful now because there are often ways to make content available to users whose browsers do not yet support HTML5.

Testing the structure of a semantic page, for example <sidebar> , and for me it is not very important. I will let them sit for another year or two.