Closed
Bug 1136280
Opened 10 years ago
Closed 2 years ago
Make getting print settings a non-blocking operation
Categories
(Toolkit :: Printing, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mconley, Assigned: jwatt)
References
(Depends on 1 open bug)
Details
We had to use a nested event loop in bug 1090439 because the print engine code is designed to get information synchronously from the operating system print settings dialog.
Nested event loops are bad. We should strive not to use them. We should investigate any possibilities to make the interface for getting print settings information asynchronous.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → jwatt
Assignee | ||
Updated•4 years ago
|
Status: NEW → ASSIGNED
Updated•2 years ago
|
Severity: normal → S3
Assignee | ||
Comment 1•2 years ago
|
||
I fixed this a while back.
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•