Closed (fixed)
Project:
Danland
Version:
6.x-2.0
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
28 Sep 2010 at 10:12 UTC
Updated:
9 Jun 2011 at 00:29 UTC
Jump to comment: Most recent file
Comments
Comment #1
danpros commentedHi,
This is z-index problem in IE:
I already fix this if using image slideshow
But since using .swf files than above code will not work since the selector is
IMGMaybe you can add this in
#menuComment #2
vmed commentedthanks,
gonna try it , will be updated
Comment #3
vmed commentedadded the z-index, is not working !
any more ?
johan
Comment #4
vmed commentedsearching the internet give me a lot of suggestions with the z-index, nothing works at all ! As you can see in the attch picture in firefox there are no problems !!
anyone any suggestions more ?
johan
Comment #5
vmed commentedThis fixes the problem:
1. Add the
to the
2.
3. Set the Container that holding the superfish menu to z-index:99. For example
4. Like above, set the flash container to z-index:0
... so explorer is ok, firefox no problem, but now safari works not fine ............!
johan
Comment #6
vmed commentedsee attch for result
johan
Comment #7
danpros commentedHi
Can you provide me the .swf files? I'll not use it just test it in Danland (my PC) :)
Comment #8
vmed commentedmail me on johan.maljaars@gmail.com
Comment #9
edcazini commentedHi,
The issue might be because of a "very old browser bug" w/c attempts to render flash objects on top of all others in a web page. The universal solution/workaround is the following:
In the
<object>tag: add<param name="wmode" value="transparent">, w/c in your case is there ...... but in the succeeding
<embed>tag you also have to put<embed>wmode="transparent" ...etc...etc... <embed>, w/c you missed.Your flash object embed code then should be like this;
Hope this helps. Cheers.
Edwin
Comment #10
danpros commentedHi Edwin,
Thanks for the info, are you already try this? at least in another theme? if yes I'll add this in handbook.
Dan
Comment #11
edcazini commentedHi Dan,
I haven't yet tested using flash in the Danland theme, but I confirm this solution/workaround works with all the other themes or pages with superfish-like (drop-down) menus with a flash object somewhere below the menu. In fact, there are quite a lot of forum threads about this drop-down-menu-hiding-behind-flash-object issue.
Btw, @johan, I missed putting the closing
</embed>tag, below is the correct code for you. It works trust me, I've played around your v-med.be site using Firefox's & Chrome's inspect element plugins.You also have an extra
</div>below the closing</object>.Some reference here, http://animation.about.com/od/flashanimationtutorials/ss/flashwmode_4.htm
Cheers.
Edwin
Comment #12
danpros commentedThanks Edwin, I already updating the handbook now.
Dan
Comment #13
edcazini commentedNo problem Dan, btw if I have the time, I'll also be doing corrections-for-the-english-language of Danland theme's handbook if you don't mind.
Danland is a veeeery nice theme, kudos.
Comment #14
danpros commentedOh, of course! I am actually glad if you or anyone willing to do so. Handbook is the property of the community, so anyone can change it to adjust to the facts.
I do not speak English from the culture so there's still much to learn. :)
Thanks,
Dan
Comment #15
beagle800 commentedI have a Similar problem, My superfish menu is going behind the banner,however it also only goes vertical and not horizontal. Take a look at the screenshot.
Everything works great in IE8,But In firefox 3.6.11 It doesn't work right
Thanks
Comment #16
edcazini commentedHi,
Your site is on Version 2.0 (Final) now, seems not using flash & not exhibiting the symptoms you describe above. So I suppose 'twas corrected now? Anyways, your 2nd issue maybe related to this one; http://drupal.org/node/951984#comment-3620960.
Cheers!
Edwin
Comment #17
koppie commentedz-index fix worked for me, thank you.
That was the original issue, so can this support request be closed?
Comment #18
koppie commentedAlmost 4 months since the last post on this issue. I suspect the original poster has moved on. I'm going to close this issue as fixed, for the sake of tidiness.