Print directly to printer should not write to mozilla.ps

RESOLVED FIXED

Status

()

--
minor
RESOLVED FIXED
12 years ago
12 years ago

People

(Reporter: panic, Unassigned)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061118 BonEcho/2.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061129 Minefield/3.0a1

When printing to a printer, postscript is first sent to the file used for "print
to file" (mozilla.ps, by default), and then sent to the printer.
This causes at least two problems:
* Users do not normally expect that one of their files is overwritten when
  printing directly to printer, and will be surprised to see that a previous
  print to mozilla.ps has been silently replaced.
* Worse, if the last file used for "print to file" was /dev/null, NOTHING is
  sent to the printer!  Setting the file to /dev/null is not unrealistic, as
  this is the only way to change print settings without printing anything.

Reproducible: Always

Steps to Reproduce:
1. Open print dialog, select "print to file"
2. Click Print
3. Enter /dev/null

Actual Results:  
Nothing is printed.

Expected Results:  
Viewed web page should be printed.

In my opinion, if printing directly to printer requires collecting postscript
in a file first, a new temporary file (e.g., in /tmp) should be created every
time.

Updated

12 years ago
Blocks: 382169

Updated

12 years ago
Assignee: general → nobody
Status: UNCONFIRMED → NEW
Component: General → Printing
Ever confirmed: true
Product: Mozilla Application Suite → Core
QA Contact: general → printing
Version: unspecified → Trunk

Comment 1

12 years ago
The fix for bug 382169 should resolve this.

Comment 2

12 years ago
The patch for bug 382169 changed how temporary files are created when printing on unix. This issue should be fixed.
No longer blocks: 382169
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Depends on: 382169
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.