Slashdot Mirror
Microsoft Finally Joins HTML 5 Standard Efforts
bonch writes "On Friday, Microsoft posted to a mailing list that IE developers are reviewing the HTML 5 standard for future versions of Internet Explorer. They've given some feedback on the current editor's draft, saying that they 'have more questions than answers' and criticizing many of HTML 5's new tags, like <header>, <footer> and <aside>, calling them 'arbitrary' or unnecessary. It remains to be seen whether Microsoft waited too long to try to influence basic parts of the spec that most of their competitors have already adopted."
The usual journalistic nightmare of a summary.
They did not call header and footer arbitrary or unnecessary. They questioned the implementation as to validity for printing.
They did call aside arbitrary as well as section.
From reading the post, I see a lot of good insights into what might be an overly-cluttered and, in places, badly written standard. While there is always an element of Microsoft playing their own games, this does raise valid questions.
Trying to become famous by taking photos. Visit my homepage please.
Microsoft's "notes" on the HTML 5 spec are [...] "This isn't detailed enough to implement concistently"
Wow, I wonder where they got that from?
Still account for at least more than 60% of users, no matter what source of statistics you use. I know for a fact, as a web developer, that if anything is wrong in a page when rendered on IE, our clients would notice instantly and file that as a bug in my code, not IE's code.
HTML is a markup language. It tells the browser "this is a paragraph" or "this is important".
Telling the browser that the top section of a website (Slashdot's tab bar) or the bottom (the search bar, quote, copyright, and links at the bottom) is exactly the sort of thing the browser should know. Screen readers would, in particular, benefit from this; most people don't need to hear the header or footer on every page.
Unnecessary? Sure - websites do fine without it. But telling the browser more about the page is a Good Thing.
I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
The video/audio tags have NOT been removed, their just wasn't a consensus on what codecs should be used, thus their is nothing specified about the codecs in the specs. You know what, that's exactly the same as for example the image-tag.
New things are always on the horizon
You should just ask what the browser can do rather than the browser name. That is the number 1 issue.
Apple has put some great information regarding capabilities detection, it can be applied to any browser not just Safari/Webkit.
http://developer.apple.com/Internet/webcontent/objectdetection.html
(no account etc. needed)