Add a comment to RenderCompositorANGLE::RequestFullRender()
Categories
(Core :: Graphics: WebRender, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
Details
Attachments
(1 file)
Bug 1637497 Comment 27 requests comments about why full render is necessary when DWM is disabled.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
When DWM is disabled, each window does not have own back buffer. They share a buffer and WM_PAINT triggers necessary re-paint. On compositor, the followings handles it.
- nsWindow::OnPaint()
- ClientLayerManager::SendInvalidRegion()
CompositorBridgeParent::RecvNotifyRegionInvalidated()
And WebRender does not support invalid region yet. WebRenderLayerManager::SendInvalidRegion()
Instead WebRenderBridgeParent::RecvInvalidateRenderedFrame() is used for now.
The following article explains about non-dwm paint.
In all versions of Windows, up until Windows XP, applications were asked by Windows to paint their visible region, and they would paint directly to the buffer that was to be displayed by the video card.
Assignee | ||
Comment 2•5 years ago
•
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #1)
And WebRender does not support invalid region yet. WebRenderLayerManager::SendInvalidRegion()
Instead WebRenderBridgeParent::RecvInvalidateRenderedFrame() is used for now.
There is a choice to call WebRenderBridgeChild::SendInvalidateRenderedFrame() in WebRenderLayerManager::SendInvalidRegion().
Assignee | ||
Comment 3•5 years ago
|
||
There is a choice to call WebRenderBridgeChild::SendInvalidateRenderedFrame() in WebRenderLayerManager::SendInvalidRegion().
Bug 1642839 is created for it.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Comment 6•5 years ago
|
||
bugherder |
Description
•