Hugene - 7:58 pm on May 31, 2010 (gmt 0)
Only browsers that support the new <input type="email"> element do anything with it.
Agreed, but the problem is that the standard does not mandate what should be done with type="email". I agree that the logical thing would be to check the validity of the email, but I am not sure that as a developer I want to leave this responsibility to the browser.
What annoys me is that if you remove the <header> or the <aside> tags from the HMTL, the browser will display the page exactly the same way as if they were there. To me, this is fluff, if a tag does not affect the rendering, then why is it there? I can't think of a single tag like this I've used.
I understand the idea of semantics and their understanding by machines, but to me, this is work we're doing for G and the other SE, and not for our end user. Anything you don't do for your user is useless.
Except that if you don't do it, your site will start dropping in the SERPs. This feels like blackmailing. For example the whole microdata push by Google. Why would I implement this, so that G can display my events listings straight on their pages?