Bug 17364
| Summary: | REGRESSION: Ignores default printer and prints to PDF | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ken McGuire <mcguire.k> |
| Component: | Printing | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap, sullivan, webkit |
| Priority: | P4 | Keywords: | InRadar, Regression |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac (Intel) | ||
| OS: | OS X 10.5 | ||
Ken McGuire
My printer default is set to a network Brother HL-2070N printer. When I select print, using WebKit, it goes to Adobe PDF 8.0, rather than the default printer. Using any URL I tried, and alternating between Safari and WebKit, when I try to print, Safari will always choose the default printer, and WebKit always chooses the PDF.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
I don't have Adobe PDF, so I haven't tried to verify.
Alexey Proskuryakov
<rdar://problem/5745309>
John Sullivan
I don't completely follow the problem here. Does "Adobe PDF 8.0" mean Acrobat Reader a.k.a. Adobe Reader? And when printing "choose the PDF", what does that mean exactly -- what appears in the Print dialog?
John Sullivan
I got the following clarification in email:
One of the choices I have for a printer is "Adobe PDF 8.0" When I select that, the output is not a printed copy, but a PDF file saved to my hard drive (or where ever I choose to save it). My system default is set for a conventional printer, and everything but WebKit prints using my default printer. WebKit ignores the default and always selects the PDF option.
John Sullivan
Do you know what software you installed to get "Adobe PD 8.0" in this list? I presume it's Acrobat Reader, but maybe not.
It seems really unlikely that this behavior was triggered by any change in WebKit. As far as I know, WebKit and Safari have no influence on the list of printers or the initially selected printer in that list. But it is certainly curious that the nightly build behaves differently than the released version of Safari.
Ken McGuire
(In reply to comment #5)
I believe it was Acrobat 8 Pro that did it, but I am not certain of that. There is no doubt that Safari and WebKit handle it differently.
Robert Blaut
*** This bug has been marked as a duplicate of 17388 ***