Hi there!
We have a Radwindow with a couple of server-controls in its ContentTemplate (i.e. a ComboBox, a TextBox...). The entire Content is ajaxified using an asp:panel directly within the ContentTemplate.
The RadWindow is opened from a RadButton via a client-side script. However, the button needs to perform a partial postback, because the controls within the RadWindiw need to be updated conditionally (server-side). Because of this, we set the RadWindow's VisibleOnPageLoad property to "true" in the button's server Click event (in order to prevent the RadWindow from closing after the partial postback).
The expected (and wanted) behavior would be:
What happens is:
What is causing the fourth step (why the annoying blinking-effect)? Any help or suggestion would be very much appreciated!!
Hans
We have a Radwindow with a couple of server-controls in its ContentTemplate (i.e. a ComboBox, a TextBox...). The entire Content is ajaxified using an asp:panel directly within the ContentTemplate.
The RadWindow is opened from a RadButton via a client-side script. However, the button needs to perform a partial postback, because the controls within the RadWindiw need to be updated conditionally (server-side). Because of this, we set the RadWindow's VisibleOnPageLoad property to "true" in the button's server Click event (in order to prevent the RadWindow from closing after the partial postback).
The expected (and wanted) behavior would be:
- Button Click
- RadWindow opens directly (javascript)
- Ajax-Loader shows, the RadWindow's content is updated and the RadWindow stays visible
What happens is:
- Button Click
- RadWindow opens directly (javascript)
- Ajax-Loader shows and the RadWindow's content is updated
- Radwindow disappears and directly reappears (blinks) <-- This is unwanted and quite annoying to the user
What is causing the fourth step (why the annoying blinking-effect)? Any help or suggestion would be very much appreciated!!
Hans