Closed
Bug 63981
Opened 25 years ago
Closed 24 years ago
Print to file doesn't verify that destination is valid
Categories
(Core :: Printing: Output, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: colol, Assigned: dcone)
Details
When selecting to Print to File instead of the print spool, Mozilla does not
appear to check if the destination file is valid or not if it is entered by
hand. Bogus (non-existant) subdirectories entered will be taken as valid and
Mozilla will exit the print dialog as normal.
To reproduce this bug:
1. Visit any site or load a local HTML file.
2. File | Print
3. Print to: File
4. Enter a path which is not valid. (Examples: if 'root' has no 'stuff' subdir,
enter /root/stuff/filename.ps. Or, make up a path completely, a la
/xxx/yyy/zzz/pr0n/1/silly.ps)
5. Click Print.
6. Verify that the file exists -- it does not.
When completed, the file does not exist, and no error message resulted.
To handle this more elegantly, Mozilla should (a) check that paths given are
valid and (b) return with an error message to the tune of "ERROR: Path does not
exist or is invalid", if appropriate.
Comment 1•25 years ago
|
||
VERIFIED
Platform: PC
OS: Linux 2.2.16
Mozilla Build: 2000122808 M18 Trunk Build
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
The solution that was proposed was to create a file mozilla.ps in home directory
of the user. This is the same behavior as 4.x. Is that acceptable solution or do
we need to ask the user to input a new location?
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 5•25 years ago
|
||
spam : changing qa to sujay (new qa contact for Printing)
QA Contact: shrir → sujay
Comment 6•24 years ago
|
||
bulk reassigning Waqar's bugs to Don.
Assignee: waqar → dcone
Status: ASSIGNED → NEW
Comment 7•24 years ago
|
||
The current 2001102503 build on Linux displays an error dialog if you enter a
bad filename when printing to a file.
Marking WFM.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•