254452 - Print dialog preferences are not persistent throughout session and must be reset everytime a page is printed.

Status: RESOLVED DUPLICATE of bug 242134

(Firefox :: General, defect)

Description

[Mike Holland]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2

Print preferences such as 'Duplex' or 'Double Sided' print must be set on every
page print. The normal Windows default is to persist such preferences during a
session. The only time preferences should need to be set again is if the browser
is closed and re-started. This occurred in a second instance of the browser with
no tabs opened in the particular instance.

Reproducible: Always
Steps to Reproduce:
1.Open browser
2.Navigate to a page
3.Select 'Print' from the 'File' menu
4.Select duplex capable printer
5.Click the 'Properties' button
6.Select 'Duplex' on 'Long Edge'
7.Click 'OK' to close properties screen
8.Click 'OK' to print page
9.Perform steps 3 thru 5 again and the selection in step 6 has been lost. 
Actual Results:  
I had to re-select 'Duplex' on 'Long Edge' again on every subsequent print.

Expected Results:  
The print preferences should have persisted until the browser or session was closed.

This is a minor bug, but to be Windows compliant it should be fixed.

Comment 1

[Andrea Aime]

I can confirm this bug, and I find it quite annoying ;-)

Comment 2

[Andrea Aime]

I can confirm this bug on Firefox 1.0, and I find it quite annoying ;-)

Comment 3

[Charles Evans]

I always get this too. Ffox 1.02, WinXPsp1.
(IE6 keeps them. )
A preference would be nice!

Comment 4

[Charles Evans]

bugs 284534 & 279028 are duplicates; 
this is nearly a year old;
can someone please confirm this? 

Comment 5

[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 6

[Mike Holland]

This bug still exists in version 1.0.7 of the software and in my opinion should
still be fixed. This bug was originally reported by me on August 5, 2004 in
version 0.9.2 of the software. The bug was confirmed November 24, 2004 by Andrea
Aime. It was confirmed/duplicated May 25, 2005 by Charles Evans for version
1.0.2. The same error was reported in two additional (duplicate) bug reports,
numbers 284534 & 279028. Although this bug is not as immediate as a security
related bug, it does still exist and should be placed on a to do list and
resolved for true Windows compliance.

Comment 7

[Jo Hermans]

*** This bug has been marked as a duplicate of 242134 ***