I'm replying here, since the threading has gone deep enough on your last response that I can't reply to it. Normally, I'd give up at this point, but I finally

I'm replying here, since the threading has gone deep enough on your last response that I can't reply to it. Normally, I'd give up at this point, but I finally see where the misunderstanding is so I'd like to make one last comment. You said: They've made it very clear the intention is to add [WebM]. I've said it's not happening overnight, and I really don't understand this attitude that if it hasn't happened instantly then everything is worse. Chrome supports WebM right now. Support for WebM and H.264 is not mutually exclusive. You can support one, you can support the other, or you can support both. That's what Chrome has done up until now: Support both. You could use either one, and it would play them back perfectly well. Chrome is not adding support for WebM. They aren't adding support for it, because they already support it and have done so for as long as it existed. Switching to a world in which everyone supports WebM in <video> tags does not require that a single browser drop support for any format--not H.264, not Theora, not anything.