Hi kabla,
The stylesheet added by the Coolite/ExtJS controls does override many default css classes. This can certainly cause problems when adding the controls to an existing project. This is something we've discussed with the core ExtJS development team and with some luck will be addressed in a future ExtJS release (v3.0?).
There are a couple ways to attempt to work-around the problem...
- As mentioned by Vladimir (vladimir), you can add a ScriptContainer control into the <head> of your Page at the position where you want the Coolite/ExtJS scripts and styles to be injected. If your styles are being overwritten, adding the ScriptContainer before your .css include *should* solve most of the conflicts.
Example
<head runat="server">
<title>ScriptContainer</title>
<cool:ScriptContainer ID="ScriptContainer1" runat="server" />
<!-- Add your .css here -->
<script type="text/javascript">
// your javascript here
</script>
</head>
<body>
<form id="form1" runat="server">
<cool:ScriptManager ID="ScriptManager1" runat="server" />
- Set the RenderStyles property to "None", and then manually add a link to the ext-all.css file as required. The following forum posts outline how/where to set the RenderStyles property.<ul>
- http://forums.ext.net/showthread.php?postid=177.aspx
- http://forums.ext.net/showthread.php?postid=178.aspx
- http://forums.ext.net/showthread.php?postid=11.aspx
Example
<cool:ScriptManager RenderStyles="None" ID="ScriptManager1" runat="server" />
[/list]All that said, there still might be some css collisions.
Hope this helps.