When you add a media item like a video to the page, it is really the wysiwyg editor that creates the markup for embedding the video. So if it is a bug it would be a bug in the editor.

The editors we use are open source editors (CKeditor and TinyMCE), so if we find a bug we have to report it upstream to the editor project.

When we do upgrades for the editors CKeditor and TinyMCE, we version the folder like /ClientScript/ckeditor36/

and the version used is configured in Web.config so if you upgraded the old version of the editor is still on disk and you could switch back to it from Web.config if you need to.

But first I would verify it by compare the markup for an existing video which works in IE to the markup of a new video that does not. If you find that the format of the embedding code is changed or wrong then it probably is a bug in the newer version of the editor and switching back may solve it.

You could also try a different editor and see if one works better than the other. From Administration > Site Settings you can choose CKeditor (the default) or TinyMCE.

Hope that helps,

Joe

Hi Mike,

If you have time it would be good to make note of the difference in the embed code generated from the newer version of TinyMCE and the old one that works and report it as bug in the TinyMCE forums.

This way we can hope to get a fix in the next release of TinyMCE.

Best,

Joe

Since it only affected IE it is probably something very small and hard to notice.

The way to document it would be

1. switch back to the new editor and reproduce the problem in IE.

2. View the source of the rendered page (not the edit page but the page that has the broken video), and copy the object/embed markup into a text file.

3. Go back to the old editor and fix it.

4. View the source of the page again and copy the markup again and paste it below the previous one in the same text file.

Then it should be possible to look very closely and compare the good markup and the bad one and find out what is different. It could be the smallest of details, but something must be a little different for one to work and the other to not work. If we could find out the difference then it would be the basis of a good bug report to submit to the TinyMCE  project.

Best,

Joe