I noticed that the weird behavior only happens with IE. But firefox does the
correct behavior (the components do not disappear from the page).
Lking wrote:
>
> Rasha,
>
> I noticed the same issue.
> Did you figure it out what's going on?
>
> thanks.
>
> On Dec 7, 2007 12:07 PM, Rasha <rasha.abdallah_at_murex.com> wrote:
>
>>
>> Hello,
>> I just upgraded to build 15, and I noticed a difference in the behavior
>> of
>> components when refreshing asynchroneously the components.
>> In build 15, the components being refreshed disappear for few seconds
>> from
>> the page and then are redrawn, which is noticeable by the user, and we do
>> not want this behavior.
>> In build 14, the components being refreshed do not disappear, and for the
>> end user it seems that only the text values have changed. Which is the
>> correct behavior.
>>
>> Note that I am using fireAjaxTransaction method to aynchroneously submit
>> and
>> refresh my components. And not refresh() and submit() functions.
>>
>> Is there any particular reason for this difference in the behavior, and
>> if
>> so, is there a way we can make components behave as in build 14?
>>
>> Thanks
>> Rasha
>> --
>> View this message in context:
>> http://www.nabble.com/Asynchroneous-Refresh%3A-different-behavior-between-build-14-and-build-15-tf4962176.html#a14212797
>> Sent from the Project Woodstock - Users mailing list archive at
>> Nabble.com
>> .
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Asynchroneous-Refresh%3A-different-behavior-between-build-14-and-build-15-tp14212797p14339601.html
Sent from the Project Woodstock - Users mailing list archive at Nabble.com.