You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2010/10/14 10:59:37 UTC
[jira] Reopened: (TRINIDAD-946) tr:panelPopup incorrect placement
in IE7 and IE6 with long pages
[ https://issues.apache.org/jira/browse/TRINIDAD-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf reopened TRINIDAD-946:
-----------------------------------------
> tr:panelPopup incorrect placement in IE7 and IE6 with long pages
> ----------------------------------------------------------------
>
> Key: TRINIDAD-946
> URL: https://issues.apache.org/jira/browse/TRINIDAD-946
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.0.5-core, 1.0.6-core
> Environment: Server: Windows 2003, Tomcat 5.5.25, JDK 1.5.0_14, Myfaces 1.1.5, Trinidad 1.0.6, Trinidad 1.0.5
> Client: IE7, IE6, Firefox 2.0.0.12
> Reporter: Jed Smallwood
>
> In IE7 and IE6 the placement of a relative positioned popup is always within the initial visible page section of the browser window as opposed to anywhere on the page. For example, my table has 50 rows. On the initial page load 12 rows are visible with my browser size. My observation is that the popup will not render below the 12th row even when the page has been scrolled down to row 50. Clicking on the popup trigger in the 50th row will render the correct popup on top of the 12th row as opposed to the 50th row.
> Viewing the same page in Firefox 2.0.0.12, all popups are rendered in the correct positions.
> After posting this to the myfaces user mailing list, Andrew Robinson responded with the following:
> I haven't had the time to look into some positioning problems with the popup, but there are many bugs in IE with regards to component location calculations.
> Open a bug
> We will need to come up with a solution where there is IE and Firefox specific JS code using bounding box code instead of attempting to use the w3c implementations which are not properly implemented by most browsers
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.