Re: [Trinidad] bad position/size of tr:panelPopup after moving from 1.0.2 to 1.0.3

[Renzo Tomaselli]

Andrew, all popups are centered and modal. I use a hidden button to trigger them. Actually there is just one popup, located inside the (single) form on the application page. I just replace panel contents by means of facelets ui:include. Things such as: <tr:document     ...     xmlns:tr="http://myfaces.apache.org/trinidad"      >     <h:form id="browser">         <script type="text/_javascript_" src=""></script>          ...         <cx:modalt bean="#{modaltBean}" container="browser:"/>     </h:form> </tr:document> where the included modal component is: <ui:component>     <c:if test="#{bean.visible}">         <tr:panelPopup id="modal" alignment="center" modal="true">             <f:facet name="trigger">                  <tr:commandButton id="modalTrigger" text="d" inlineStyle="visibility: hidden" />             </f:facet>             <cx:include src="" bean="#{bean.componentBean}" container="#{container}"/>         </tr:panelPopup>     </c:if> </ui:component> Browser behavior is: - IE 6/7: vertical position/height are ok. The right border always matches the right window border. The left border is somewhere in left half window. - FF 2.0: height ok. Top=0, left=0, width = full window. I can debug what the renderer is doing wrong, just let me know where to start. -- Renzo Andrew Robinson wrote: There were _javascript_ changes to this popup. Could you be more exact with the problem? Where is the popup showing in relation to the center of the screen (modal dialogs should be centered)? Where is the form that the dialog appears in, in relation to the screen? Is the location exactly the same in IE 6/7 and FF 2? Is there any scrolling on the HTML, BODY or FORM elements? Thanks, Andrew On 10/29/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: Hi, after moving an application from 1.0.2 to 1.0.3, I noticed that all modal panel popups are now rendered in a wrong position and width. Height is ok. With version 1.0.2 they used to appear ok. This behavior is browser-independent (IE 6/7, FF 2.0). Just flipping the Trinidad jar pair between 1.0.2 and 1.0.3 toggles this behavior. -- Renzo