Good call on recommending a tool like Firebug, Brooks. As for your feeling that "cf9 messed up" a tag, I'll just throw out that when I hear an assertion that, especially about a tag that involves CF generating HTML that calls back to the server for files like these might, I'd suggest there's possibly not a problem with CF itself, rather with that mechanism that's calling back to the server. And that often has its root in one of two possible problems.
First, there could be a problem in the configuration of the web site, so that the browser calling back to the needed CFIDE directories may be finding the wrong one for the version of CF being executed for the page. It's easy for some people to tweak their web config to have a given site point to a virtual directory for CFIDE (which could be the wrong version) or they may have made a duplicate of the CFIDE (for use by a given site) but then forgot to update that when they updated CF. Second, related to that last point above, there could be a problem that was introduced when a hotfix was added: it's very easy to apply hotfixes either only to one CFIDE, or to the wrong one. I discuss that and related matters in a blog entry here: http://www.carehart.org/blog/client/index.cfm/2011/10/21/why_chfs_may_break Of course, in this case, a tool like Firebug may still show a "successful" communication between the browser and server, but the version of the file or library obtained by the server may just not be the "right" one for the other HTML/JS/CSS that CF generated, when it assumed it was generating it for a specific version of such files/libraries. Hope that may help, whether Dusty, Brooks, or anyone else. /charlie PS Besides Firebug, there are also now built-in tools in most modern browsers that can help to see the communications. I blogged recently about that: http://www.carehart.org/blog/client/index.cfm/2012/3/20/builtin_browser_prox y_sniffer_tools I also list there a link to my cf411 category on still other such browser proxy/sniffer tools that can be added, if needed. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, April 27, 2012 10:09 AM To: [email protected] Subject: Re: [ACFUG Discuss] cfwindow - how to change the grey border in the header? Dusty: First off, I can't seem to get <cfwindow> to work properly, it looks like CF9 has messed that tag up. I've seen that with <cflayoutarea> as well. That being said, I think the solution to your problem can be accomplish by overriding the "x-window-header" and "x-window-body" styles that ColdFusion is using. I would try to wrap the <cfwindow> tag in a named <div> element like this: <div id='myStuff'> <cfwindow name="window1"> blah, blah, blah </cfwindow> </div> Then include a stylesheet entry like #myStuff .x-window-header { border: 1px solid blue; /* or whatever */ } #myStuff .x-window-body { border: 1px solid blue; /* or whatever */ } Firefox - FireBug plugin is really good at letting you see (and dynamically) change the styles for a page element. This should get you started. Sincerely, Brooks ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
