Add support for print preview

[GoogleCodeExporter]

It'd be nice to add support for print preview to CEF.  At the moment, CEF 
allows you to print the contents of a frame, but CEF creates and manages the 
device context itself.  In order to handle print preview, I think we'd want a 
function like PrintToDC that would allow a client to pass in an HDC and page 
number (or CefDeviceContext, to keep it platform-neutral).  CEF would render 
the given page to the DC, but not actually print anything.  The client could 
then use the rendered DC to display a print preview window.

Original issue reported on code.google.com by emerick on 15 Sep 2010 at 8:32

[GoogleCodeExporter]

Original comment by magreenb...@gmail.com on 29 Sep 2010 at 2:17

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I too wery interested this tool support. In chrome this work/ What to do that 
in CEF it work's too?

Original comment by vipc...@gmail.com on 4 Apr 2012 at 10:56

[GoogleCodeExporter]

I need this tool. It's very important for cef.

Original comment by long....@gmail.com on 17 Apr 2012 at 7:09

[GoogleCodeExporter]

so what's the plan?

Original comment by xzoth2008@gmail.com on 2 Apr 2013 at 6:13

[GoogleCodeExporter]

Do we have any thoughts on an initial approach for this? The project I'm 
currently working on requires some type of print preview, so I'm interested in 
potentially adding this to CEF3, but I probably need some pointers on where 
exactly to start.

Is the functionality that Chrome uses to render PDFs for print preview 
available to us in CEF or is that unavailable in Chromium?

Original comment by emerick on 15 May 2014 at 3:13

[GoogleCodeExporter]

@comment#5: The Chrome PDF plugin uses custom pepper extensions and is not open 
source, so we can't (easily) use it with Chromium.

Original comment by magreenb...@gmail.com on 15 May 2014 at 3:26

[GoogleCodeExporter]

Google open sourced (BSD) the Chrome PDF rendering engine just a few days ago, 
see PDFium:
https://code.google.com/p/pdfium/

Original comment by czarek.t...@gmail.com on 23 May 2014 at 10:29

[GoogleCodeExporter]

PDFium already got into Chromium's trunk:
http://src.chromium.org/viewvc/chrome/trunk/src/pdf/pdfium/

Interesting, this is the same rendering engine that is used in Foxit PDF 
Reader, the documentation link from wiki page leads to Foxit SDK.

Original comment by czarek.t...@gmail.com on 23 May 2014 at 10:44

[GoogleCodeExporter]

Wow, that's fantastic news. Marshall, I assume this would be a good way forward 
for this?

Original comment by emerick on 23 May 2014 at 1:16

[GoogleCodeExporter]

@comment#8-9: Yes, good news. If we're lucky this will become part of the 
Content API in the context of 
https://code.google.com/p/chromium/issues/detail?id=311308.

Original comment by magreenb...@gmail.com on 23 May 2014 at 9:06

[GoogleCodeExporter]

Do we need a separate issue in the Chromium issue tracker for migrating print 
preview support to the Content API? Just asking because the item you mentioned 
explicitly limits its scope to exclude print preview.

Original comment by emerick on 23 May 2014 at 10:20

[GoogleCodeExporter]

Starting with https://crbug.com/170859 Chromium now uses PDF instead of 
metafiles for printing. We'll need to figure out how to move printing in CEF to 
PDF as well.

Original comment by magreenb...@gmail.com on 11 Jun 2014 at 9:13

[GoogleCodeExporter]

@comment#11: I added a question about print preview support at 
https://code.google.com/p/chromium/issues/detail?id=311308#c9

Original comment by magreenb...@gmail.com on 11 Jun 2014 at 9:26

[GoogleCodeExporter]

CEF is transitioning from Google Code to Bitbucket project hosting. If you 
would like to continue receiving notifications on this issue please add 
yourself as a Watcher at the new location: 
https://bitbucket.org/chromiumembedded/cef/issue/123

Original comment by magreenb...@gmail.com on 14 Mar 2015 at 3:20