example tags got stripped

It may seem pointless now with today’s technologies, but surely it creates potential for new, more intelligent applications in the future. After all, what I call you may call at least this way we’re all doing the same thing.

Isn’t this exactly what we’re trying to solve with Microformats? To give more meaning to something which has none? div div div div div div. Search engines could start spidering things differently, disability devices could get users to what they’re looking for faster.

Everyone should actually create a page in Html5 then style it before they comment on it.

-Tateman

If Silverlight is their reason for not implementing it then perhaps then HTML 5 developers should adopt the same stance that Microsoft do.

If a user goes to a Silverlight website but doesn’t have Silverlight installed, they’re greeted with a ‘please install Silverlight’ message. What’s to say that HTML 5 developers can’t do the same? “Please upgrade to a standards compliant browser such as ___”

The only difference is that Microsoft have the advantage of being able to disguise Silverlight as an ‘Important Update’.

Microsoft finally decided to share the IE team thoughts on HTML5, unfortunately their feedbacks are mostly negative, and are a bit late for some elements they are arguing. The IE team could have argued these elements long a…

And you know what? If this is a first of a long series of posts from the IE team, I will be happy, we certainly need them there! But if they are gonna step out of the closet one time a year and say, we have concerns about that, fix this, and go away, for me, not good enough!

The point of MS with unnecessary tags is that they do not behave different than normal divs and that the spec is not detailed enough. Are you allowed to user more than one nav section? Sure. But is there a way to determine which of these sections is the primary navigation that is intented to be used by screen readers or search engines? Nope. So what’s the point with these tags? Semantic tags only make sense, if you are able to determine the semantics Like h1…h6. Those are clear. With nav it still depends on the human to determine the meanings.

The comment about header / footer makes sense, too. Those two would be perfect for printing, but there’s no word in the spec how exactly or if those tags affect printing.

I just don’t get the keygen tag at the moment. It seems to be about creating certificates. If so, it doesn’t matter if we have complex forms, web 2.0 or captchas. I guess I need to read some more on the topic, because currently I don’t see any relation between the tag and yout comment.

Your point about the events fails completely! Seems like you didn’t read it properly. That paragraph is in the feedback to the bb tag. That one is supposed to be inside the body tag and should have all the usual events which in their view is a security risk. They suggest to put a link tag with a reference to an application manifest in the header part, so it’s not part of the DOM. I fully second that. There’s no sense for meta information to appear inside the body.

It seems to me, that most of the commnentators on this post didn’t read the post. So here we have it: http://lists.w3.org/Archives/Public/public-html/2009Aug/0389.html.

Additionally he doesn’t say “we don’t implement it”. He is about “we have concerns if this is the right way”. And if you read the replies you will find, that Jonas Sicking of Mozilla shares at least the concern about the bb tag and that it won’t be implemented by Mozilla! Another point the IE team mentions (the datagrid) was removed from the spec the same day. HTML5 is not finished yet, it’s still in the works.

Strange that you hear MS talk about innovation…. they clearly have a whole other interpretation about it than the greater part of the community.

btw microsoft? How’s DOS doing? Still running, nice…. very nice?

“it will prove useful as web developer will be able to indentify website sections more quickly”

This isn’t really the function of a HTML tag, Cedric. HTML Comments are there for us to make code more human-readable, but the HTML itself is there to be read by a browser.

If the browser is going to treat a HEADER the same as a DIV and a FOOTER and an ASIDE, why should we have 4 different tags when adding class=”header” would do just fine.

Are we gaining any extra functionality from a HEADER element that we can’t get from DIV class=”header”?