I find out that RadFormDecorator adds its classes rfdRoundedCorners rfdDecorated after an ajax call.
Let's say I have a couple of RadTextBox and a checkbox inside a <div> wich will be ajaxified.
I want to style the checkbox so I add RadFormDecorator.
On the first page load, my RadTextBoxes will have just their classes: riSingle RadInput (plus eventual specific skin) When I trigger the ajax postback and the div updates the same textboxes will have rfdRoundedCorners rfdDecorated classes added by the form decorator. This may seem like an "innocent" behaviour but is not since this will change your css specificity. So if for example you override textboxes css with: html body .RadInput .riTextBox, html body .RadInputMgr { }
This will work on a fresh pageload but won't work anymore after the ajax update, screwing up the rendering of the textboxes.
A quick fix is of course to add !important inside the css overrides, but I'm wondering if this behaviour is intended and if there is some easy workaround instead of using the !important clause in our css.
Thanks in advance
I want to style the checkbox so I add RadFormDecorator.
On the first page load, my RadTextBoxes will have just their classes: riSingle RadInput (plus eventual specific skin) When I trigger the ajax postback and the div updates the same textboxes will have rfdRoundedCorners rfdDecorated classes added by the form decorator. This may seem like an "innocent" behaviour but is not since this will change your css specificity. So if for example you override textboxes css with: html body .RadInput .riTextBox, html body .RadInputMgr { }
This will work on a fresh pageload but won't work anymore after the ajax update, screwing up the rendering of the textboxes.
A quick fix is of course to add !important inside the css overrides, but I'm wondering if this behaviour is intended and if there is some easy workaround instead of using the !important clause in our css.
Thanks in advance