Yes but google and chrome are simply picking and choosing what parts of the "standard" they implement (it's not a standard right now anyway, it's a draft). And when that happens it's very risky, look what happened to Netscape's guesswork with the Layer tag
- developers had to code around a broken, non-compliant implementation for years because a browser company decided to jump the gun in order to get a competitive advantage. MS also learnt this the hard way with their XML bits. Mozilla's threading bits aren't
part of any standard at all, they're the new <blink> tag.
It's interesting to note who is driving the standard - Google and Apple, people who complained loudly when MS tried to implement new non-standard bits but are happy to do it themselves. Heck Google already said they would try to push for additions to HTML5
to support Wave - and that's very worrying, a company influencing a standard just to suit one of their applications.
"Google and Apple, people who complained loudly when MS tried to implement new non-standard bits but are happy to do it themselves."
Are you comparing Active X, bogus PNG support and JScript to a partial HTML5 implementation?
What Microsoft implemented was based on nothing outside of their walls, and it's sole purpose was to promote the lack of browser compatibility(clone and superset) in order to manipulate people into exclusively using it's products forever.
Without JQuery and other libraries which abstract away IE, we would still be using the web in 1998 mode, right where Microsoft wants us.
"One must ask, is Microsoft ignoring the standards process or the standards process ignoring Microsoft?"
Microsoft is waiting and seeing because all else has failed.