Linked by Kroc Camen on Thu 29th Apr 2010 23:04 UTC

Thread beginning with comment 421687
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
As for the codec, the w3c backed off specific codecs now for the spec, so its up to the implementors.
Only at the insistence of Apple. W3C originally specified Theora, and Apple threw a hissy fit and vetoed that. Since there is no other competitive royalty-free video codec available at this time, the W3C have been unable to include the codec specification as yet within the HTML5 specification.
This in turn is a major reason why HTML5 is not yet a W3C recommendation.
The codec is NOT up to the implementors. One cannot have a royalty encumberence within a web satndard, so there is no agreed standard as yet.
Perhaps if Google make VP8 royalty-free, then this situation can be resolved. Or maybe Theora can be agreed upon eventually. Whatever ... h264 is NOT it.
Member since:
2006-02-05
Ok, so they embraced HTML5 video. They didn't extend any standard, that would be implementing the video tag by calling it ms-video or something stupid, and giving it a different javascript api then everyone else.
As for the codec, the w3c backed off specific codecs now for the spec, so its up to the implementors. Not only that, but what apple is doing is having a worse effect at this point - you can download chrome on windows which supports both, but if you are on an iDevice (which dominates the mobile web), it is h264 only.
If they had done something like implement the video tag with WMV only support, then I would probably agree with you, even though it still doesn't really fit.