HTML5…I am not digging it at all…
For the people who read the title and are going to moan about how awesome the video/audio tags are and what not, go read the ENTIRE article of the elements of HTML5…here is the link.
Then come back and lets talk…mmmmmkay?
Is it still awesome? I’m going to give you a ‘for instance’ here. Let’s start with…the address tag. When you hear “address” tag, what do you think of? What would you put in this tag? Before you read that article, you probably thought “Well, the freakin’ address you idiot!” Guess what though? You would be wrong. Quoted from the article:
“The address element must not be used to represent arbitrary addresses (e.g. postal addresses), unless those addresses are in fact the relevant contact information. (The p element is the appropriate element for marking up postal addresses in general.)”
Through a bunch of searching and head scratching I finally found an awesome example. Let’s say I create a page about contacting Senator Stupid about Health Care Issue #1, the address tag should contain MY contact information. Now let’s say Senator Stupid has his own page about Health Care Issue #1, then HIS contact information would go in the address tag.
Confusing? YES! The address tag is for information concerning the article/page whatever, NOT the postal address of whoever owns the site…or whatever. UNLESS of course it pertains to the article/page itself. STUPID! This kind of crap bugs me.
I thought HTML5 would be for people to read the actual HTML more easily. These new tags though (although I’ve read the address tag has been around since the beginning) have all these crazy rules. Like when you can use the aside tag, how to structure the sections so that it creates a specific outline, and other such craziness. If anything, HTML5 has complicated the HELL out of everything.
I guarantee that when this is fully adopted, 90% of the web developer population will be using half the tags in the wrong way. They will think, address tag, that MUST be where I put my address. The section is like the left side, the right side, top and bottom. The nav is for any navigations…
Wait…now you are thinking “Um…isn’t it?” Ya….here’s another quote from the w3:
“Not all groups of links on a page need to be in a nav element — only sections that consist of major navigation blocks are appropriate for the nav element. In particular, it is common for footers to have a short list of links to various pages of a site, such as the terms of service, the home page, and a copyright page. The footer element alone is sufficient for such cases, without a nav element.”
The word “need” there confuses the crap out of me. I want a yes or a no. Do I put all navigations in the nav tag or not?? Apparently if it is in the footer tag, you can do without it. So really, I am lead to believe that there is only one place for the nav tag, and that is the main navigation on the page. If I have 2 or 3 sub navigation areas, these apparently do NOT go in a nav tag. Do they? How many people do you think are going to read the w3 document? And how many nav tags do you think you will see on a bigger page? On the ones I work for at work, I can count at least 4 spots where someone would put that tag if they were not aware of the “rules.”
If you reaaally want to see how confused people are just on the address tag, go read and start laughing at the comments on this article.
When you have done that, you will realize NO ONE knows what the hell we are in for. I certainly don’t. After reading the w3 HTML5 page, I am scared that even they don’t know what they are talking about.
NOTE: I should have titled this “HTML5…why we are all f#@$ed!”