Note that there are some explanatory texts on larger screens.

plurals
  1. POHTML div display on top of Flash Object
    primarykey
    data
    text
    <p>I have a flash slideshow with 2 divs overlaying it, one at the top and one at the bottom. </p> <pre><code>&lt;header&gt; &lt;div id="top-menu"&gt; &lt;ul&gt; &lt;li&gt;Main Menu Link&lt;/li&gt; &lt;li&gt;Main Menu Link&lt;/li&gt; &lt;li&gt;Main Menu Link&lt;/li&gt; &lt;/ul&gt; &lt;/div&gt; &lt;header&gt; &lt;div id="content"&gt; &lt;div id="slideshow_wrapper"&gt; &lt;section id="intro"&gt; &lt;p&gt;Introduction Text&lt;/p&gt; &lt;/section&gt; &lt;section id="slideshow"&gt; &lt;!--dynamically inserted flash object--&gt; &lt;/section&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p>Both overlay properly in Firefox/Safari/Chrome, but nothing I try seems to make it work in IE. I'm using <a href="http://remysharp.com/2009/01/07/html5-enabling-script/" rel="nofollow">Remy Sharp's HTML 5 enabling script</a> to make the HTML5 mark-up work in lower versions of IE. What's funny is that the second div, <code>#intro</code> overlays correctly, but <code>#top-menu</code> always appears behind the` slideshow.</p> <p>All 3 elements are absolutely positioned with z-indexes explicitly set. No matter how high or low I set them the flash object is always in front of the <code>#top-menu</code> element.</p> <p>I have checked the rendered <code>&lt;param&gt;</code> tags and one of them lists <code>wmode</code> as <code>transparent</code>. </p> <p>The flash object is dynamically inserted with php through a CMS, so I have no access to the <code>&lt;embed&gt;</code> tag that many have suggested adding the <code>transparent</code> attribute to.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload