HTML5 and bad example of “same markup”
From the Apple website:
I’m not a marketing guy. My mind beats “developer, developer, developer”. And as a developer, I can’t stop thinking that this pop-up is very sad.
Don’t get me wrong. It’s great for Apple to promote their browser. Everyone has a preference. At least, I do :-)
BUT – it’s sad to see that the demo that they are claiming are built on HTML5 web standards don’t run on any browser, but Safari.
What is a web standard?
Can a browser that render well a website with browser specific code and markup (for instance, using 177 vendor prefix extensions in just one CSS file) and prevent you from seeing it in other browsers (*) claim to support “web standards”?
I’m scared by this trend to call “open, reliable, secure and efficient” any new work in progress over the W3C Specifications. Browser vendors have a big responsibility, which is not demonstrating how quickly their developers can write code over night.
Web browsers should render the same markup – the same HTML, same CSS, and same script – the same way. That’s simply not the case today. Enabling the same markup to work the same across different browsers is crucial for HTML5’s success.
What do you think?
Update 11:29 – (*) As expected, playing with Fiddler and Developer tools to change the User Agent, the Apple HTML5 site (purified by Safari-specific markup and code) looks equally awful on Firefox, Chrome, Opera and IE. Not exactly the goal of W3C with HTML5…