When switching printers, reset any prepopulated settings from the previous print that are not valid for the new printer
Categories
(Toolkit :: Printing, defect, P3)
Tracking
()
People
(Reporter: Lenp, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [print2020_v81])
![]() |
||
Updated•7 years ago
|
Updated•6 years ago
|
![]() |
||
Comment 2•5 years ago
|
||
This was filed against the dialog based UX, but the new doorhanger UX should be especially careful to do this.
![]() |
||
Updated•5 years ago
|
![]() |
||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
We filed bug 1658450 to refresh the printer settings when it changes. The error I was getting with the Save to PDF option seemed to be that we were copying over settings that we shouldn't copy over (but only after you've used the old print dialog, interestingly).
We'll stop copying the settings over, but we need to figure out what to do with the other settings. If I change settings to my liking then realise I'm printing to the wrong place (and they're reasonably equivalent) I'd rather use my changes than the last used for that printer. Perhaps for now we should just throw all the changes away and refresh just to be safe.
![]() |
||
Comment 4•5 years ago
•
|
||
There may be some hidden settings in the nsIPrintSettings object if you initialized it from a previous printer. I would expect those to be overwritten if you switch to another actual printer, but switching to 'Save to PDF' may not overwrite something significant.
It would seem to make sense to me to behave as follows (possibly modulo optimizations to step 2 and 3 to avoid unnecessary overwriting):
- create a settings object using the default settings for the newly selected printer
- overwrite that with any settings that have been saved for that printer
- overwrite that with any settings set in the UI, but "clamped" to be valid based on any restrictions imposed by the printer (whether it supports the currently selected paper size, duplex, margins, etc.)
![]() |
||
Comment 5•5 years ago
•
|
||
We'd normally duplicate the newer bug to the older bug, but since bug 1658450 has a patch I'll dup this over to that one in this case. Thanks for the report, Len.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
(Actually, maybe this one is a real dupe. Apologies for the bugspam!)
Description
•