'Print to file' not working correctly when printing silently

RESOLVED EXPIRED

Status

()

RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: joery.olthuis, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: Mozilla 1.7

I'm using Mozilla 1.7 embedded in a Microsoft Win32 application.

My application supports several document types, each associated with its own 
print settings. This requires me to show a print dialog only once for each 
document type. After that, the printSilent setting is set to true. This works 
fine when printing to a printer, but not when 'print to file' is specified. 
I believe this has to do with two problems:

1. nsDeviceContextSpecWin::CheckForPrintToFile ignores the 'print to file' 
setting as well as the return value of nsIPrintSettings::GetToFileName. 
Instead, it uses the printer name to determine whether printing to file is 
wanted, which I believe to be incorrect.

2. nsPrintSettings::CheckForPrinters fills in a valid printer name. So even if 
I fill in a filename instead of a printer name to satisfy 
nsDeviceContextSpecWin::CheckForPrintToFile, this still doesn't work because 
it is overruled by nsPrintSettings::CheckForPrinters.

I haven't tested this, but I guess the user might be able to print to file if 
the 'print silent' setting is off, because this causes a print dialog to be 
shown not until after nsPrintSettings::CheckForPrinters has done its job. 
Clearing the 'print silent' setting is not an option for me though, so I 
currently have no workaround.

Reproducible: Always
Steps to Reproduce:
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
reporter is gone - support at oclcpica.org writes "we are no longer interesested in these bugs, since it is such a long time ago. But thanks annyway. Yours sincerely, Servicedesk"
You need to log in before you can comment on or make changes to this bug.