If you should be front-end custom or a veteran XHTML/CSS coder, you realize when purchasing the framework of the web site the DIV tag is probably the only most flexible format component.
Using the release of HTML-5, we will have appropriate labels to exclusively manage these same issues, like headers and so forth.
Will its use decrease? Could it be deprecated permanently?
HTML was awesome, but HTML-5 is even better. The brand new HTML-5 spec states the DIV is actually not being deprecated, but more view should be used by writers when working with them. Actually, the language of the specification says towards the impact of, until there’s simply no other appropriate element do not utilize it.
We realize you will find semantically correct label things to select from, and we all know the DIV tag isn’t being deprecated.
Then when could it be suitable to utilize a DIV?
Take a case of the format. You and you might have an article part and links for sharing the content, respectively. The links refer to the article, but they’re unrelated to this content of the article. To be able to possess the links arranged correctly, this could be considered a great use to get a DIV. Furthermore, using footer labels and the new header, they can’t include headers and footers themselves. If you have to arrange several symbols or links within the footer work with a DIV.
In other words, you need to start understanding when it is suitable when they represent some of one’s information to make use of the brand new semantic label things, instead of unthinkingly covering it in a DIV. Let us observe that is set to use:
Everyone reading your code can quickly place the brand new area from the identification. Rather than DIV having an identification of “footer”, you merely include the brand new “footer” tag.
Anticipate that DIVs it’s still applied even to provide the impact of printed key in columns, or to cover whole pages in a pot. DIVs will play with an important part in installing your site content and planning. The brand new specification only claims which you think about the new components first, and use them before using a DIV when they make semantic sense.