Hi,

The only issue that I noticed which is important to have fixed in the 
1.2.3 rc ( at least for our project ;)
is the panelPopup with modal=true in FF2. AFAIK it is fixed in 1.0.3, 
according to below attached mail,
and so I assume it will also be in 1.2.3 hopefully :-)

We have been working with a 1.2.3. SNAPSHOT for a while and it seemed 
rather stable to us.
So I would vote for a go at 1.2.3rc (again, provided above fix is 
contained ;)

Best wishes,
Wolfgang.

On 10/16/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: 
hi,

I am still behind my mails, but noticed that a 1.2.3-branch has been
created. I'd like to ask for a timeframe for when we can try to 
release a 1.2.3, based on this branch.

Are there any (big) know issues?
Did someone used it for testing already?

Thx,
Matthias

----- Weitergeleitet von Wolfgang Toepfer/PTA_GL/De am 16.10.2007 15:01 
-----

"Andrew Robinson" <[EMAIL PROTECTED]> 
11.10.2007 18:08
Bitte antworten an
"MyFaces Discussion" <[email protected]>


An
"MyFaces Discussion" <[email protected]>
Kopie

Thema
Re: [Trinidad] tr:panelPopup broken in Trinidad 1.2.2 with FF 2.x ? 






1.2.3 will have some large position fixes. 1.0.3 already has them.

On 10/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> For your information, as I am not sure wether this is a known problem
> or just a configuration issue on my side.
>
>  I tried a simple popup such as
>
> <tr:panelPopup text="Auftragsselektion!" title="Gefundene Auftraege"
> alignment="center" modal="true">
>
>                 <tr:outputText value="Do you want to finish?" />
>
>
>
>                                  <trh:rowLayout>
>
> <tr:commandButton accessKey="1" text="1:Cancel"
>
> action="fXAbbrechen"/>
>
> <tr:commandButton accessKey="2" text="2:Ok"
>
> action="f1Change"/>
>                                    </trh:rowLayout>
>
>  </tr:panelPopup>
>
> However, this only works in IE 7 but not in FF 2.x. In FF the behaviour 
is
> strangely buggy: the mouse pointer
> switches to a "prohibited" symbol and everything is disabled apart from 
FF's
> close button. BTW there is no
> Javascript error.
>
> Any ideas regarding this behaviour?
>
> Thanks,
> Wolfgang.
>
>

Reply via email to