155589 - Windows Print Quality Setting Not Honored

Status: RESOLVED WORKSFORME

(MailNews Core :: Printing, defect)

Description

[Tim Johnson]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1a+) Gecko/20020629
BuildID:    2002062908

I have my print quality set for draft mode. I recently upgraded from Mozilla 1.0
to this build. Now when I print an e-mail, the print quality appears higher than
draft mode. If I print the same e-mail from Mozilla 1.0, the print quality is
draft as expected.

Reproducible: Always
Steps to Reproduce:
1.Write an e-mail to yourself, and send it.
2.With the print quality set to draft, print the received e-mail.
3.Note the print quality.

Actual Results:  Print quality higher than the draft mode that was set.

Expected Results:  Print quality of draft mode.

Comment 1

[dcone (gone)]

Mozilla does not use this setting, I think that is purely a printer driver
setting.  If its not coming out draft then the printer is responsible for that.
 The internals of mozilla dont do anything differently (never have) based on
this setting.

Comment 2

[Tim Johnson]

Well, have you tried to reproduce this problem by comparing print quality when
on draft setting between Moz 1.0 and 2002062908? BTW, I still see this problem
with 2002070404. Nothing about my print driver has changed.

Bottom line is that this works (Draft setting print draft quality, not higher
quality) with Moz 1.0 and NOT with the latest nightly builds.

Comment 3

[Tim Johnson]

Here's another data point. Starting with my plain text test e-mail, from the
Print dialog I selected "Acrobat PDFWriter" instead of "HP Deskjet 610C". I then
"printed" to a pdf file. From the Acrobat Reader, I printed the page, again with
my print quality setting still at "Draft". This printing came out in with the
expected draft quality. More evidence that Moz is doing something different when
printing to my real printer. And, as I said originally, this change occurred
since Moz 1.0.

Comment 4

[Tim Johnson]

I've tested this again with the 2002071504 nightly, and the problem seems to
have been resolved. Thanks to whoever fixed it.

Comment 5

[Kai Lahmann (is there, where MNG is)]

l