Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: open
"The problem we're facing right now is there is already a lot of excitement for HTML5, but it's a little too early to deploy it because we're running into interoperability issues," including differences between video on devices, said the official, Philippe Le Hegaret, W3C interaction domain leader. He is responsible for specifications like HTML and SVG (Scalable Vector Graphics).
[edited by: incrediBILL at 3:48 am (utc) on Oct 7, 2010]
[edit reason] Added quote [/edit]
Does this mean that everyone drinking the iKool-aid will end up with HTML 5 that has interoperability issues just to look cool on iDevices, or that iWebkit will now be the defacto leaders in supporting quirks caused by deploying HTML 5 too fast?
As it is backward compatible with both HTML and XHTML syntax, does that mean it solves the problem of using XHTML output (from framework or CMS) when you cannot use application/xhtml+xml?
We won't see another IE6-like situation again. It was created by a lack of foresight, similar to the Y2k bug. Nobody is going to upgrade from IE6 to IE7, they will go to the most current browser and the circumstances that led to the current problem are most likely removed.