Bug 1848357 - Remove PaintWhileInterruptingJSNoOp(). r=mconley
This should not be needed anymore. We no longer need to "ack" an epoch, since there's no epoch. Make the logic to trigger a paint and request composite a bit more generic. That doesn't change behavior right now, because our visibility state is tied to mRenderLayers, but without this change setting renderLayers = true on a display: none iframe will trigger a useless paint after bug 1847584. Differential Revision: https://phabricator.services.mozilla.com/D187293
This commit is contained in:
@@ -3750,14 +3750,6 @@ void BrowserParent::LayerTreeUpdate(bool aActive) {
|
||||
frameElement->DispatchEvent(*event);
|
||||
}
|
||||
|
||||
mozilla::ipc::IPCResult BrowserParent::RecvPaintWhileInterruptingJSNoOp() {
|
||||
// We sent a PaintWhileInterruptingJS message when layers were already
|
||||
// visible. In this case, we should act as if an update occurred even though
|
||||
// we already have the layers.
|
||||
LayerTreeUpdate(true);
|
||||
return IPC_OK();
|
||||
}
|
||||
|
||||
mozilla::ipc::IPCResult BrowserParent::RecvRemoteIsReadyToHandleInputEvents() {
|
||||
// When enabling input event prioritization, input events may preempt other
|
||||
// normal priority IPC messages. To prevent the input events preempt
|
||||
|
||||
Reference in New Issue
Block a user