Remove nsWindow::mPaintDC.
Categories
(Core :: Widget: Win32, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(3 files)
| Assignee | ||
Comment 1•2 years ago
|
||
It's unused.
| Assignee | ||
Comment 2•2 years ago
|
||
| Assignee | ||
Comment 3•2 years ago
|
||
There's no real reason to do this, and other browsers don't either. This
is in preparation for further simplifications to how we deal with
transparent windows (because they're now pretty broken,
see bug 1850979).
Comment 6•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/092f81f39e6a
https://hg.mozilla.org/mozilla-central/rev/ab71e5c57a38
Comment 8•2 years ago
|
||
| bugherder | ||
Comment 9•2 years ago
|
||
External apps may use WM_PRINT/WM_PRINTCLIENT to take a screenshot of our windows. I don't think we can remove the WM_PRINTCLIENT handler based on our internal usage.
| Assignee | ||
Comment 10•2 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #9)
External apps may use
WM_PRINT/WM_PRINTCLIENTto take a screenshot of our windows. I don't think we can remove theWM_PRINTCLIENThandler based on our internal usage.
Can you elaborate? We don't paint synchronously so how does that work exactly? Why do other apps not need it? MSDN says that windows such as controls need to implement it, and that some APIs like AnimateWindow need it, but it doesn't say anything else and we're neither afaict.
| Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Sorry, I was wrong.
- Cross-process
::SendMessage(WM_PRINT(CLIENT))does not work. ::PrintWindow()usesWM_PAINTinstead ofWM_PRINT(CLIENT)contrary to the documentation.
So external apps have no way to use the WM_PRINTCLIENT handler of Firefox.
| Assignee | ||
Comment 12•2 years ago
|
||
Cool, thanks for checking tho, and for the answer! (you're definitely more familiar with all this stuff than me).
Description
•