Ok, I know it's been months since I started this thread, but I had to put this project on hold for quite awhile, and also wait for my IT guy to install the latest update to CF on the server to make sure that wasn't the cause of the problem.
The problem is still happening. Since it's been so long, let me repeat what it is: A site I am working on uses the cfdocument tag to create PDFs of pages. The pages that are being converted are very image-heavy, and all of the images are floated, using CSS. They also have CSS clears on them to ensure that if one image wants to start before the previous one has ended they don't get "hung up" on one another. This works great in the HTML, but sometimes -- not always -- the clears are not respected in the PDFs that cfdocument outputs. I see no pattern in which images get caught on previous images. Here's a PDF that exhibits the problem: <http://www.saferoutesinfo.org/guide/tpo_pdf.cfm?ITEM=Page&CHAPTER_ID=C353&Page=tools_to_reduce_crossing_distances_for_pedestrians.cfm&PageTitle=Tools%20to%20Reduce%20Crossing%20Distances%20for%20Pedestrians> (Second image doesn't clear at all, other images on pages 3 and 4 almost clear but get hung up) Here's the page that the PDF was created from: <http://www.saferoutesinfo.org/guide/engineering/tools_to_reduce_crossing_distances_for_pedestrians.cfm> Here's the style sheet that styles the PDFs: http://www.saferoutesinfo.org/guide/css/pdf.css Jon Clausen had this suggestion: >Also, I've personally found that I sometimes need to "brute force" >the CSS for cfdocument PDF's. By that, I mean calling all your >selectors as specifically as possible and using "!important" more >liberally than you might on an HTML page to override any default >styling. An example using your CSS: > > >div#content img.right { > /*display: inline;*/ > clear: right!important; > float: right!important; > margin: 0 0 .8em 1em; > margin: .2em 0 1em 1.4em; >} > >instead of > >.right { > /*display: inline;*/ > clear: right; > float: right; > margin: 0 0 .8em 1em; > margin: .2em 0 1em 1.4em; >} Unfortunately, using !important on my clear declaration, as well as changing it to clear: both, has not made any difference. I'm thinking at this point that there is nothing else I can do -- cfdocument is just too buggy. But I wanted to follow up on this thread once more just to make sure no one else had any ideas. Thanks, Zoe ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268320 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
