Comments on: CFDocument and CSS Hell http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/ ColdFusion, Ant, jQuery and other geeky stuff with the occasional motorcycle post. Thu, 28 Aug 2008 09:20:50 +0000 http://wordpress.org/?v=2.6 By: Julian Halliwell http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3415 Julian Halliwell Mon, 20 Aug 2007 07:52:41 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3415 Jim, try using the file protocol with a file system path to the stylesheet: [link rel=”stylesheet” type=”text/css” href=”file:///#expandPath(myCssDirectory)#docstyles.css”] Note the 3 slashes, not 2. This is vital. Also, my understanding is that only html 4.0 is supported in cfdocument (ie not xhtml). Jim, try using the file protocol with a file system path to the stylesheet:

[link rel=”stylesheet” type=”text/css” href=”file:///#expandPath(myCssDirectory)#docstyles.css”]

Note the 3 slashes, not 2. This is vital.

Also, my understanding is that only html 4.0 is supported in cfdocument (ie not xhtml).

]]> By: Jim http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3413 Jim Fri, 17 Aug 2007 14:01:34 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3413 OK - FWIW - I get the same behavior with @import. I still have to include it within each cfdocumentitem, etc - no different than using link... OK - FWIW - I get the same behavior with @import. I still have to include it within each cfdocumentitem, etc - no different than using link…

]]> By: Jim http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3412 Jim Fri, 17 Aug 2007 12:55:54 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3412 Not running CF8 (yet)... Tony - I'll try using an import vs. a link to call my CSS. I've updated the post above with my final solution - and it seems to work OK. And FWIW - none of my cfincluded documents include any doctype, head/body, etc... Not running CF8 (yet)… Tony - I’ll try using an import vs. a link to call my CSS. I’ve updated the post above with my final solution - and it seems to work OK. And FWIW - none of my cfincluded documents include any doctype, head/body, etc…

]]> By: Tony Petruzzi http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3411 Tony Petruzzi Fri, 17 Aug 2007 03:10:39 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3411 First off Jim is correct, you need to have a fully valid HTML page in order to get cfdocument to even remotely render correctly. I would recommend (and what I personally do) is create your page statically first with some dummy data and then validate it against the w3c validator. Make sure your using XHTML 1.0 Transitional, that seems it to work best. The final step is DO NOT use link on inline styles within your cfdocument, you MUST use import to load your css. This was mentioned to me a long time ago and I've always remembered it. It's saved me a bunch of time and frustration. First off Jim is correct, you need to have a fully valid HTML page in order to get cfdocument to even remotely render correctly.

I would recommend (and what I personally do) is create your page statically first with some dummy data and then validate it against the w3c validator. Make sure your using XHTML 1.0 Transitional, that seems it to work best.

The final step is DO NOT use link on inline styles within your cfdocument, you MUST use import to load your css. This was mentioned to me a long time ago and I’ve always remembered it. It’s saved me a bunch of time and frustration.

]]> By: TJ Downes http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3410 TJ Downes Fri, 17 Aug 2007 02:27:48 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3410 agreed. Are you perchance running CF8? I found cfdocument far better with CF8 than 7, even with existing apps. agreed. Are you perchance running CF8? I found cfdocument far better with CF8 than 7, even with existing apps.

]]> By: Jim http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3409 Jim Thu, 16 Aug 2007 17:27:44 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3409 The problem is these pages are just content - there is no HTML header/footer, etc. I could maybe generate a printer friendly index.cfm and call that with CFDcoument - but that seems like extra work I shouldn't have to do. The problem is these pages are just content - there is no HTML header/footer, etc. I could maybe generate a printer friendly index.cfm and call that with CFDcoument - but that seems like extra work I shouldn’t have to do.

]]> By: TJ Downes http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3408 TJ Downes Thu, 16 Aug 2007 17:21:31 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3408 You're not doing anything wrong there. What you're doing is exactly what you should be :) An alternative is to have a generated HTML page and then use cfhttp to get that page and then use it to create the cfdocument. You might find this produces more reliable results and allows you to use a stylesheet You’re not doing anything wrong there. What you’re doing is exactly what you should be :)

An alternative is to have a generated HTML page and then use cfhttp to get that page and then use it to create the cfdocument. You might find this produces more reliable results and allows you to use a stylesheet

]]> By: Jim http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3407 Jim Thu, 16 Aug 2007 16:37:49 +0000 http://www.thecrumb.com/2007/08/16/cfdocument-and-css-hell/#comment-3407 What would be nice is if I could do: cfdocument stylesheet = "print.css" What would be nice is if I could do:

cfdocument stylesheet = “print.css”

]]>