[ 
http://issues.apache.org/jira/browse/MYFACES-693?page=comments#action_12331908 
] 

Werner Punz commented on MYFACES-693:
-------------------------------------

I checked the code for the popup component, it indeed does not use the iframe 
fix which is necessary to bypass the
div over drop down bug of the IE releases, I will try to fix it for the trunk 
first, since it is less critical there.


> select Combo Box is displayed over popup component instead of hiding behind
> ---------------------------------------------------------------------------
>
>          Key: MYFACES-693
>          URL: http://issues.apache.org/jira/browse/MYFACES-693
>      Project: MyFaces
>         Type: Bug
>   Components: Tomahawk
>     Versions: 1.1.0, 1.1.1
>  Environment: Client is Windows XP and IE. No problem with Firefox.
> Server is Linux with Tomcat 5.5
>     Reporter: Marcel Sansaricq

>
> html select input elements are displayed in front of the tomahawk popup 
> component  in IE. The problem is not present in Firefox.
> As I was searching the MyFaces mailing list  for a solution to the problem I 
> found a similar issue discussed in the following link:
> >http://www.mail-archive.com/users@myfaces.apache.org/msg05344.html
> In the excerpt below from the discussion, the problem was fixed for the 
> suggest component currently being developed by Werner Punz in the Sandbox:
> "Incidentally, I'm looking into modifying the DHTML piece so that you can 
> avoid the IE bug where a select box is always rendered on top of a div. It 
> turns out that if you create an invisible iframe as a shim of sorts, directly 
> underneath the div, select boxes will properly render underneath it. Of 
> course, this fix is only necessary if you're using the control near a select 
> box, and if you care whether your form renders properly in IE, so it'll be 
> optional.) 
> Well solved that a few days ago as well :-), thanks to some articles on the 
> net."
> I am hoping that the fix used for the suggest componenet in the sandbox can 
> be reused to address this issue. I downloaded the latest release candidate 
> RC2 verified that the problem is still present in both the release 1.1.0 and 
> 1.1.1.
> Thanks in advance for you help.
> Marcel

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to