radwindow frame/edge transparancy/invidible problem

2 posts, 0 answers
  1. JJ
    JJ avatar
    147 posts
    Member since:
    May 2010

    Posted 16 Feb 2011 Link to this post

    I use radgrid, click on a link on the radgrid to open a radwindow on the top of the radgrid. Sometimes, the radwindow frame/edge is kind of transparancy/invidible, can not see the close button, but the close button is actually there, just has no color.

    It is very strange. The problem only happens to some of the user/browser while using the same web app on the server. Sometimes, the problem happened on me, but not on someone else using the same web application, but the other day, happened to someone else.  

    Not sure how this will happen. It never happen on my local box while in development. Only happens when move the the servers.



    telerik:RadWindowManager runat="server" ID="RadWindowManager1"




    VisibleStatusbar="false" Height="600px" Width="800px"














    <telerik:RadWindow ID="TranslationView" runat="server" OnClientClose="OnClientClose"




    NavigateUrl="TagLanguageVerticalView.aspx" runat="server" VisibleStatusbar="false"



    Title="Translation View">










    <telerik:RadWindow ID="History" Top="20" Left="100"




    runat="server" NavigateUrl="History.aspx" VisibleStatusBar="false" Title="History">
















  2. Georgi Tunev
    Georgi Tunev avatar
    7207 posts

    Posted 21 Feb 2011 Link to this post

    Hello JJ,

    Basically, what you report is happening in 3 cases:
    1. RadControls are using external skins - in such scenario, it is not unlikely that the imported CSSs on the page exceed 31 which cause the CSS added after that number, not to be applied on the page. Because alphabetically, RadWindow is usually added at the end, its skin my not be loaded properly.
    2. The CSS could not be loaded because of a permission problem. To check that, I suggest to use Fiddler or a similar tool to examine the response from the server and to see whether or not the CSSs are loaded.
    3. You load the controls using Ajax, but before showing a control (RadWindow in this case), for some reason you make a postback. In such scenario, you need to make sure that EnableAjaxSkinRendering is set to true before you show the control.
      Here is how EnableAjaxSkinRendering works:
      When a control is loaded with a postback, it automatically set its skin files (css) in the head of the page.
      When a control is loaded with Ajax however, since there is no postback, the head section is not updated and that is why a control rendered with Ajax must output its skins somehow. When the EnableAjaxSkinRendering property is set to true (by default it is true) and the control is loaded with Ajax, it outputs the CSS on the page and there is a client-side code that "puts" the CSS in the head section. After that, the EnableAjaxSkinRendering property is automatically set to false in order to avoid outputting the CSS again when you load it multiple times. If at some point however, you are submitting the form without Ajax, this property will stay set to false, hence the problem next time you open the window.

    I hope this information helps

    All the best,
    Georgi Tunev
    the Telerik team
Back to Top