Closed
Bug 1641733
Opened 4 years ago
Closed 4 years ago
Re-engineer the reftest harness to initiate printing via the parent process
Categories
(Core :: Printing: Setup, task, P2)
Core
Printing: Setup
Tracking
()
RESOLVED
FIXED
mozilla79
People
(Reporter: jwatt, Assigned: hiro)
References
(Blocks 1 open bug)
Details
(Whiteboard: [print2020_v79])
Attachments
(1 file)
reftest-content.js currently invokes printing by calling nsIWebBrowserPrint.print in the content process. For Fission we need to initiate printing in the parent process, so we need to change this code to initiate the print via the parent where it can call nsFrameLoader::Print.
|
Assignee | |
Updated•4 years ago
|
Assignee: nobody → hikezoe.birchill
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
Pushed by hikezoe.birchill@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/897ccfd1ec0c Trigger print via FrameLoader.print in the parant process instead of in the content process. r=jwatt
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
|
||
Comment 5•4 years ago
|
||
| bugherder uplift | ||
status-firefox-esr78:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•