Hi Matt,
Matt Raible wrote:
The easiest way to solve this problem (with Struts Menu) is to add
onmouseover events to menu-config.xml that hide the offending elements.
Thanks for the reply. I've seen that method mentioned around the
traps. I may have to do it, but unfortunately there are a lot of
elements on a lot of pages that will need to be covered off. I have
also seen an article about a technique involving the use of a hidden
iframe that you put between your "popup" component and everything else.
Unfortunately I've found the Appfuse menu stuff a bit beyond my current
CSS and JS skills to try and work out how to incorporate such a
solution. It sounds like it would be a more attractive solution to the
problem if it could be made to work.
I'll have to leave this one for now as I have more pressing problems
elsewhere.
On Dec 17, 2007, at 9:27 AM, Rob Hills wrote:
Hi All,
I'm using Appfuse 2.0 + Struts 2. In my project, I'm using the
"standard" horizontal nav menu used by the default AppFuse 2 theme.
I'm having a problem with elements "bleeding through" the dropdown
menus and not only is it unsightly, but it causes functional problems
because you can't select a drop-down menu item that has an underlying
component on top of it.
I've been doing some googling and reading about the problem and I'm
aware of issues with "combo" controls appearing on top of
everything, but this problem affects other HTML elements as well.
For example, I have a button that's an <img> component with an
onclick event and this appears on top of a dropdown menu that's
supposed to go over the top of it. Another element that causes the same
kind of problem is a <th> with a background image (from the stylesheet).
I've seen the problem in both FireFox (current version) and Internet
Explorer 6. I've used Firebug to try and examine exactly what's going
on with the CSS to cause this, and I've tried playing around with
z-indexes, but they don't seem to make any difference.
Unfortunately, my css skills are not really up to diagnosing this
problem but I can't believe no-one else has seen the problem and I'm
hoping someone who knows their CSS better than I do has already fixed
it.
Has anyone else seen this problem?
Cheers,
Rob Hills
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
