Closed
Bug 1067504
Opened 11 years ago
Closed 11 years ago
Make nsDocumentViewer::SetPrintPreviewPresentation correctly handle attaching to toplevel widgets
Categories
(Core :: Print Preview, defect)
Tracking
()
RESOLVED
FIXED
mozilla35
| Tracking | Status | |
|---|---|---|
| e10s | m3+ | --- |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
|
1.58 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
This is needed for bug 927188. Otherwise we never attach the print-preview presentation in the child process to the puppet widget and end up not painting it.
| Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8489521 -
Flags: review?(bugs)
| Assignee | ||
Comment 2•11 years ago
|
||
It's not clear to me, by the way, whether it's best to do this, or to set it up in the print code wherever we create the viewmanager... This seemed pretty sane and safe to me, though.
Updated•11 years ago
|
tracking-e10s:
--- → m3+
Comment 3•11 years ago
|
||
Comment on attachment 8489521 [details] [diff] [review]
Hook up print preview to our parent widget as needed, so it will actually paint.
Looks pretty sane. The view handling stuff in printengine doesn't currently
deal with printpreview explicitly, and since SetPrintPreviewPresentation
is explicitly for pp, this should be fine.
Other option is to modify nsDocumentViewer::MakeWindow and nsPrintEngine::SetRootView( quite a bit.
Attachment #8489521 -
Flags: review?(bugs) → review+
| Assignee | ||
Comment 4•11 years ago
|
||
Yeah, I'm all in favor of not modifying things more than needed here. ;)
Comment 5•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in
before you can comment on or make changes to this bug.
Description
•