Closed Bug 4638 Opened 26 years ago Closed 24 years ago

Printer dialogs don't stick

Categories

(Core :: Printing: Output, defect, P3)

Product:
Core
Component:
Printing: Output
Platform:
Other
Linux
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: sujay, Assigned: slogan)

References

Details

(Keywords: platform-parity)

using 4/5 build of apprunner on Linux. Please re-assign to appropriate person. thanks! In 4.x, printer dialog settings stick which means if the user for example brings up the print dialog, selects "to file", browses around and selects e.g., /tmp/foo the next time the dialog comes up, the default file is /tmp/foo. Our defaults are someone hardcoded; we need to remmeber previous settings and use these to seed subsequent invocations of the print dialog.
changing QA_contact to myself....sorry for all the bug mail spam!
Assignee: syd → dcone
Status: NEW → ASSIGNED
Summary: Printer dialogs don't stick → [PP]Printer dialogs don't stick
Target Milestone: M7
Target Milestone: M7 → M10
Component: Apprunner → Printing
Blocks: 11275
Assignee: dcone → syd
Status: ASSIGNED → NEW
Sorry for the spam, changing QA contact on printing bugs to our new printing tester, Shrirang!
Mass moving these bugs to M13
Target Milestone: M13 → M15
Moving Syd's non-PDT+ bugs to M15 to indicate that he will not have time to get to them for Beta.
Keywords: pp
Summary: [PP]Printer dialogs don't stick → Printer dialogs don't stick
Fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I still see the problem on m15 branch build for today on linux. (2000041213). Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
How come this is still M15? M15 is already out!
Target Milestone: M15 → M16
Mass moving old milestone bugs to M16
M16 has been out for a while now, these bugs target milestones need to be updated.
Fixed
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Verified fixed (2000062908)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.