Concerning particularly RadGrid
, here is an online demo showing
the control with no predefined and rendered CSS classes and no
predefined styles. The control will take up any table-related CSS
styles that you add to the web page.
I would also like to throw some light on the discussed topic about inline styles and predefined CSS classes.
Due to some specifics of the browsers, a given control's functionality and its HTML rendering, there may be a need for some CSS styles to be applied in all cases, no matter what the control's skin is. These are the so called "base" or "common" styles. Most of the RadControls have them and in most cases, if these base styles are not applied, the control will not look even close to what it should. One should not forget that RadControls are more complex than the
standard ASP.NET framework controls, so the more complex HTML rendering
also requires more complex styling, which in some cases cannot be
simply stripped in full. RadGrid is an exception, as it has no base stylesheet and its layout is mostly "self-created", because it is table-based.
This is the main reason why RadControls render some amount of inline styles and/or CSS classes even when Skin="".
One can set Skin="" and EnabledEmbeddedBaseStyleSheet="false" and in this case a control will be displayed "as naked as possible" and will not register any CSS files. Thus, it will be easily stylable by generic CSS code. Indeed, some inline styles and CSS classes may still be rendered, but they will not prevent the generic CSS code from being applied. On the contrary, they should facilitate the creation of suitable CSS selectors to style the control. Some controls, e.g. RadSlider, are not suitable for styling by generic CSS code, as RadGrid is, so it will be impossible to use those controls without a single CSS class rendered.
I dare say that the way RadControls are currently implemented, with respect to HTML and CSS, suits the vast majority of our customers, which are specialized in server-side development and prefer to not care about the controls' HTML output, CSS classes, styling, etc. Simply changing the embedded skin is enough for them. In almost all cases, custom skins are created by copy-pasting an existing skin and making some changes here and there. So these people are greatly facilitated by the existence of predefined CSS classes, inline styles and base stylesheets.
Surely, we are always open to feedback and suggestions, and I thank you for sharing your opinion and experience with our products.
Let us know if you need additional information.
All the best,
the Telerik team