Closed
Bug 291493
Opened 20 years ago
Closed 20 years ago
Printing errors with Acrobat 7.0 plugin
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: wjones, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 SUSE/1.0.3-0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 SUSE/1.0.3-0.4 Some PDF documents don't print correctly using the Acrobat 7.0 plugin for Firefox. Mozilla 1.7.7 has identical problems. The same documents will print correctly using Acrobat as a stand-alone application, or as a plugin for Konqueror. Reproducible: Always Steps to Reproduce: 1.Load the sample URL using the Acrobat 7.0 plugin 2.Print page 10. Actual Results: One user at our site gets a large black box that obscures a line drawing in the printed output. Another user gets a Postscript error from the printer (Error: /invalidaccess in --setfileposition--). There is no problem with the on-screen display. Expected Results: Correct printed output, as with standalone Acrobat 7.0 or Konqueror plugin. Results are the same whether Postscript level 2 or level 3 is selected. If the problem page is printed to a file, the resulting Postscript causes an error in kghostview or gv. However, ggv will display the Postscript file correctly.
Updated•20 years ago
|
Assignee: bugs → printing
Component: OS Integration → Printing
Product: Firefox → Core
QA Contact: os-integration
Version: unspecified → 1.7 Branch
Comment 1•20 years ago
|
||
Although the page may print ok from standalone acrobat reader, this still looks like an Adobe bug. The plugin does its own printing entirely. The closest thing I could find to feedback on the Adobe site was the online forums: http://www.adobe.com/support/forums/main.html resolving this INVALID for now. If you can identify something more specific Mozilla is doing wrong, feel free to reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•