I'm sorry, but that post does not apply to our problem (although it's interesting). We are already using css classes, but our problem is that as soon as an async postback is made, all those css settings are lost.

Here's an example:

I have an Infragistics UltraWebMenu in a Master Page, I want the items to have a certain style. I use a class for this, called "menuItem", asigned in ItemStyle in the markup part of the master page.

when the page renders, it does like this:

 

class

 

= " ig_d4377750_r2 menuItem"

and it shows exactly what I want. But then, when the user clicks in a toolbar option, a datagrid gets filled, and the styles I defined are ignored and only the ones defined in ig_d4377750_r2 are used.

This started to happen only when we migrated from v6.3 to v8.2

 

dvanzo said:

class = " ig_d4377750_r2 menuItem"

The class "ig_d4377750_r2" is a CSS class that was automatically generated by one of our controls (WebMenu, in this case).  This is precisely the scenario that I discussed in my previous update.  The ID, "ig_d4377750" in this case, changes from callback to callback, but the dynamically-rendered CSS (in the HEAD of the page) cannot be updated during an asynchronous callback.

To address this, you need to explicitly define a CSS class for all of the relevant Style properties used on our controls, and make sure that this CSS is included in your page during the initial callback.  Alternately, you can use Application Styling, which will handle creating and connecting the CSS for you.

mmhh... I can see now that you where right.. the problem was actually in our css files, that in v6.3 were being ignored and now in v8.2 are taken into account, and they were different to what we thought!

Thanks for your time!