205943 - Printing in Mozilla Browser with HP LaserJet 4+ - print one page with duplex option turned off, then print another page and duplex is reset to printer default.

Status: RESOLVED EXPIRED

(Core :: Printing: Output, defect)

Description

[M. Beckett]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Printing in Mozilla Browser with HP LaserJet 4+ - print one page with duplex
option turned off, then print another page and duplex is reset to printer
default. Under Netscape, the settings are allowed to be changed in one session
from the printer defaults and stay on for subsequent prints

Reproducible: Always

Steps to Reproduce:
1.File -> Print
2.Select page 1 to 1
3.Click on "Properties" button
4. Under the "Print on Both Sides(duplex)" heading unselect the printer default
"Flip on Long Edge" by selecting the "None" radiobutton
5. Select OK to print
6. When I print out another subsequent page the duplex option is reset to the
system default in the same browser session

Actual Results:  
2nd + all next prints reverted to printer default for duplex

Expected Results:  
In the same browser session, the default should have been changed for all
prints, like in the Netscape browser

Comment 1

[Larry Cook]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122

I have always experienced this problem since at least 1.3, maybe earlier, and
stil have the problem with 1.8a5.  And I don't think it's specific to the printer.

In addition to having it remember the duplex setting for the duration of the
session, it would also be nice if the Page Setup dialog allowed you to change
this property so that it would be saved to prefs.js so that it would persist
across sessions.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.