Everyone is anticipating for HTML5 to roll out! The folks at YouTube are well aware how hot HTML5 will be, and so they are releasing the new embed code style for YouTube videos to accompany HTML5 and mobile environments. On YouTube’s blog, it says something of sort that the new embed code style is not yet a default method for embedding YouTube videos, but the code is working and you can try it out to see how well the new embed code style works. The new embed code style allows YouTube videos to be streamed in HTML5 environment and on mobile devices. When HTML5 environment and mobile devices aren’t available, the new embed code style allows YouTube videos to be streamed in Flash. This means the new embed code style will work with all environments!
New YouTube embed code style uses iframe. An example of new code style will look like this. If you got a browser that support HTML5, try to watch the video in this post. If your browser isn’t supporting HTML5, the video in this post is still going to play, but it will be played in Flash format.
I found out that adding YouTube’s new embed code style in WordPress’s posts will not work! WordPress is stripping away the iframe code completely when you’re switching from the HTML editor mode to the Visual editor mode. There is only one way to make YouTube’s new embed code style works with WordPress’s posts is to switch to WordPress’s HTML editor, stay within the HTML editor mode, add the code, and do not switch back to the Visual editor mode ever for the very post you’re editing. The iframe code for YouTube’s new embed code style will stick within a WordPress’s post this way!
This is a big drawback for WordPress users! You never know by accident that you’re re-editing a WordPress’s post which has had YouTube’s new embed code style in the Visual Editor mode. When that happens, you’re sure to lose a YouTube’s video in a post. Trying to remember the exact embed code that you lost in the post would be a hard thing to do!
Why I’m ranting on about YouTube’s new embed code style has a conflict with WordPress software? It’s because I’m using WordPress to write this very post! What a bummer right? Source.