Closed
Bug 1359298
Opened 8 years ago
Closed 7 years ago
[Mortar] [Windows] Investigate if replaying EMF could avoid the slowness issues
Categories
(Core :: Printing: Output, enhancement)
Core
Printing: Output
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: fatseng, Unassigned)
References
Details
No description provided.
Reporter | ||
Comment 1•8 years ago
|
||
There is a information in Chromime code.
It is related to using FPDF_RenderPage() of PDFium lib.
They met performance issues when calling FPDF_RenderPage() with a printer DC.
Create this bug to investigate if we have a chance to meet the issue when replaying EMF on printer DC.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1345710#c83
https://cs.chromium.org/chromium/src/pdf/pdfium/pdfium_engine.cc?rcl=9ad9f6860b4d6a4ec7f7f975b2c99672e02d5d49&l=4008
// A "temporary" hack. Some PDFs seems to render very slowly if
// FPDF_RenderPage() is directly used on a printer DC. I suspect it is
// because of the code to talk Postscript directly to the printer if
// the printer supports this. Need to discuss this with PDFium. For now,
// render to a bitmap and then blit the bitmap to the DC if we have been
// supplied a printer DC.
Comment 2•7 years ago
|
||
I'm closing this bug as WONTFIX per:
"The Mortar experiment has concluded. Mozilla does not consider the PDF use case justifies the burden of implementing and maintaining PDFium and a Pepper API implementation in Gecko."
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•