We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
we have problems with PDFs created with cfdocument (CF 11) and the Microsoft Edge Browser.
Edge shows only a white page.
Here is the Link to a Sample Document, please try it on Edge:
The same PDF, but opened and saved with Acrobat DC.
This PDF is shown in Edge
What can we do to create compatible PDFs also for Edge with cfdocument?
Thanks in advance
Please show example code used to create the PDF document. That way we can try it in our environment and see what result we get.
we use <cfpdf action="ADDWATERMARK to merge our letterhead with the created content from cfdocument to our final invoice PDF.
<cfpdf action="ADDWATERMARK" destination="#application.docpath#\fbRechnungen\Rechnung_FB#dateformat(redatum, "yy")##dateformat(redatum, "mm")##dateformat(redatum, "dd")#-#id#.pdf" source="mydocument" copyfrom="#application.docpath#fbDocs\RE_background_INT.pdf" opacity="10" overwrite="Yes" showonprint="Yes"></cfpdf>
Here is our letterhead:
Are you saying that if you don't add the watermark then the resulting PDF works correctly in MS Edge?
This wouldn't surprise me at all. Certain PDF features will prevent PDFs from rendering in browsers. The way CF implements watermarks is not the same as how Acrobat itself does it.
Dave Watts, CTO, Fig Leaf Software
Yes that's right.
The PDF created with cfdocument works correctly in MS Edge
But the combined watermarked PDF doesn't.
We use this method for many years and had no problems so far, until now with Edge.
As a matter of interest, if you serve only the "RE_background_INT.pdf" file as the response to the Web request, does MS Edge display it correctly?
If not, try opening it and re-saving it on the server with Adobe Acrobat. It is possible that file itself is the source of the problem.
I can confirm that using CF11, Internet Explorer, Google Chrome and Mozilla Firefox successfully show the resulting PDF document, but Microsoft Edge does not.
thank you for your support.
Is this a bug in CF11 or in Edge?
That means for us we have to create our documents completely in one cfdocument-statement.
HTML in cfdocument is very tricky, but i think for now this the only option.
Best regards and greetings from Vienna