cf_window (extJS) and css

Posted At : January 9, 2008 7:16 AM | Posted By : Trond Ulseth
Related Categories: DHTML / Javascript, CSS, ColdFusion
In my work I'm working on a site where many companies will be presented, and each company should be able to go in and edit their own details.

I wanted to avoid a solution where each company would have to log into the FarCry administrator (as most sites we do this one is also made using FarCry CMS). So I decided to have a login link on each company presentation site. As I came upon this blog post I decided to try cf_window and have the login form come up in a window instead of the login link leading to a separate login page.

Within minutes I had a nice looking login window on the site. However I noticed that some other elements in the page did not look as (good as) before. A quick check with Firebug showed that a css file /cfext/ext/resources/css/ext-all.css now was linked to and that this file setting some general css styles (like the size of all header elements to be font-size:100%

I don't know if this is standard extJS behavior, but this is BAD (leave my CSS alone!).

So I just went ahead an commented out line 9 - 15 in this css file and all is now good :)

Comments (2) | Print | Send | del.icio.us | Linking Blogs
Comments
[Add Comment]
First off thanks for checking out the project. The big problem with the css there is that I am pulling all of the css files which do include the reset files. When I get closer to a release It will just include the files needed an you will no longer have that problem. I guess order should come into play as well, did you have your stylesheets declared after the ext:include?
# Posted By Dan Vega | 1/9/08 8:27 AM
@ Trond & @Dan: I had to comment out the same ext-all.css lines as well (9-15). I have some very specific layout margins etc for my app, and it has to run in IE6 as well.

@Dan: RE: Stylesheet Include Placement...unless you manually place your own CSS links in the <body> tag, they will always come before the ones from your include.cfm. This is because CF always places all CFHTMLHEAD includes AFTER the "manually created" lines. Great stuff none-the-less...I like what you have done with the include/widget system as well.
# Posted By Troy Allen | 1/10/08 9:21 AM
[Add Comment]