RadAjaxManager pb with css on callback

3 posts, 0 answers
  1. CSurieux
    CSurieux avatar
    465 posts
    Member since:
    Jan 2007

    Posted 24 Nov 2008 Link to this post


    I was not experimenting this before Q3, using AjaxManager on a page I found in my trace that on ajax callback triggered by a RadTreeView node drop, after call back result being sent, some process clientside is trying to reload all the css from my theme.

    I don't know why, this seems useless and factor of slow answer ?
    css from theme are well loaded and behaving correctly on first page display (isPostback false), and they continue being ok after each callback, why trying to reload ?????

    More, the reloading generates an error because I am using an url rewritter and the reloading do not use a correct path as writen in <header>  ( whiche looks like href="../../App_Themes/Web20/mycss.css") but a changed one as  http://Host:Port/MyRewriterTag/MyRewriterPageId/App_Themes/Web20/mycss.css 
    and it generates a 404.

    As I don't need to reload all this, how to tell RadAjax not reloading hearder on callback ?
    It is certainly a known issue with Q3 ?

    As a subidiary question: is there a way to compress all theme css in only one file to speed initial loading, to day i get one link for each css file ?

    Thanks for answer.

  2. CSurieux
    CSurieux avatar
    465 posts
    Member since:
    Jan 2007

    Posted 25 Nov 2008 Link to this post


    More info, I found an apparent solution as I am using net 3.5 sp1,
    I change the Form.action to the url before rewriting and I don't get the 404 errors due to bad urls for css, css files from my theme do not seem to be reloaded.

    I think it is totally crazy: when I set into form.action an inexistant url, I don't get the 404 not found errors because no reloading is done.
    And if I let form.action whitout modification, it get the real url (rewritten) in form.action, but this fact seems to triggers reloading of all css from theme after a callback, the reloading being done with the unexisting url made for the rewritter...

    Seems that browser is doing a check on the submit url in form.action to see if some css has to be reloaded, but the url to reload from (application relative ?) is not taken from same place ?

    If somebody could explain :
    1) on what conditions css from theme are reloaded after a callback ?
    2) which url is taken (from which value) to reload css ?
    3) who is responsable of this MS or Telerik ?

  3. Maria Ilieva
    Maria Ilieva avatar
    4017 posts

    Posted 27 Nov 2008 Link to this post

    Hi Christian,

    We are not aware of such issue and it actually the first request we received about this behaviour.

    Could you please let us know if the problem appears in some specific browsers or it is valid for all of them? Also please check if the browser stored its cache or it is disabled?
    Regarding the header reload you could use the "EnablePageHeadUpdate Property" of the Ajax controls in order to modify this behaviour. 

    Sincerely yours,
    Maria Ilieva
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Back to Top