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

[Renzo Tomaselli]

Andrew, till 1.0.2. it was "alignment=none, center" (see http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_panelPopup.html). As such, it was working perfectly until I moved to 1.0.3, where this attribute appears becoming "position=relative,centered". I just tried to turn it to "position=centered", but it still doesn't work: now behavior is the same on all browsers, but width is still nearly full window. It seems that browser_modal_popupContainer clientWidth is setup to be such width. -- Renzo Andrew Robinson wrote: There is no "alignment" attribute of panelPopup. I believe you are looking for position. <tr:panelPopup position="centered" ... On 10/29/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: Andrew, a bit of more info from Firebug: in spite of declaring alignment="center", is see that TrPanelPopup.showPopup() is called with arg position="relative" instead of "centered". This call comes from page loading, where I simulate trigger activation by and simply: click: function(trigger) { trigger = document.getElementById(trigger); if (trigger) trigger.click(); } next TrPanelPopup.show() still refers to this wrong attribute, using event positioning. Hope it helps. -- 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