Closed
Bug 331636
Opened 20 years ago
Closed 19 years ago
Setting for default printer not honored in Solaris
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: ck, Unassigned)
Details
(Whiteboard: CLOSEME 06/27)
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.8.0.1) Gecko/20060206 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.8.0.1) Gecko/20060206 Firefox/1.5.0.1
When multiple printers are defined, Firefox prints to the most recently used value of $MOZ_PRINTER_NAME when PostScript/default is selected in the print dialog, rather than using the Solaris system default printer. (When this variable is unset -- e.g., immediately after Firefox is launched -- the system default printer will be used when PostScript/default is selected. However, after any other printer has been used, the most recently used printer becomes PostScript/default.)
Reproducible: Always
Steps to Reproduce:
1. Launch Firefox
2. Print from Firefox to a printer other than the system default printer.
3. Print from Firefox to PostScript/default.
Actual Results:
The print job in step 3 is spooled to the printer used in step 2, above (i.e., the most recent value of $MOZ_PRINTER_NAME).
Expected Results:
he job should be sent to the system default printer whenever PostScript/default is selected in the print dialog.
Note that this is more serious than a simple loss of functionality. It is a potential security issue: it could result in the improper disclosure of confidential information if, for example, a sensitive document wound up on a shared printer without the user realizing it.
Comment 1•19 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
Comment 2•19 years ago
|
||
-> Closing as incomplete because of missing feedback if this is still reproducible in the latest release (Firefox 2.0.0.4) or Trunk Build.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•