Embeded video showing up in footer

Posted by yogayak on December 19, 2008 at 11:24pm

When I embed video it's shows up somewhere around the footer only as in http://dev5.playpoi.com/node/41

Pictures adding show up in the proper place.

Anybody have an idea what why only the embeds would show up there?

Love and light,

Michel

Comments

It could be a number of

Posted by New Zeal on December 20, 2008 at 2:52am

It could be a number of things: CSS, or even some kind of script that is interfering with the embed object. You would need to have someone get a handle on your site and troubleshoot it.

Passing Phase Web Development

I just tried your page and

Posted by MacRonin on December 20, 2008 at 4:50am

I just tried your page and the vimeo video seemed to load in the correct place. definitely not in the footer. I was using a Mac 10.5 with Safari

-------------------
http://www.PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://www.SunflowerChildren.org/ Helping children around the world ( Drupal)

-------------------
http://PrivacyDigest.com/ News from the Privacy Front (Drupal)
http://CongressionalResearchReports.com/ Bringing you the research that your taxes already paid for. ( Beta/Drupal)

And works in Chrome

Posted by yogayak on December 20, 2008 at 2:45pm

Silly me, I just assume that Firefox always gets things right!

It works in Chrome as well.

Thanks, this will help debug.

love and light,

michel

Browser Testing

Posted by DeeZone on December 23, 2008 at 8:52am

Michel,

Run the site through http://browsershots.org. You'll see that all the browsers based on the Mozilla rendering engine produce flaky results. Based on the code that's output in Firefox I'd would say the issue is at line 274:

<p><object width="480" height="385"></p>
<param name="movie" value="http://www.youtube.com/p/D2D136CEFCBDD59A"></param><embed src="http://www.youtube.com/p/D2D136CEFCBDD59A" type="application/x-shockwave-flash" width="480" height="385"></embed></object></p>

Note the p tags are invalid, they're nested around the object tag. Based on what exists for the problem node entry this is not what is entered. I think there's a bug in one of the modules that is rewriting the HTML producing invalid markup. Firefox is simply doing it's job :)