Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
2011-02-03 Anders Carlsson <andersca@apple.com>
Reviewed by Dan Bernstein. Change DidSetSize to take a LayerTreeContext parameter https://bugs.webkit.org/show_bug.cgi?id=53724 Since SetSize can cause layout to happen, we need to pass along a layer tree context to the DidSetSize message so the UI process can enter/exit accelerated compositing mode appropriately. * Shared/LayerTreeContext.h: * Shared/mac/LayerTreeContextMac.mm: Add equality operators to LayerTreeContext. * UIProcess/DrawingAreaProxy.h: (WebKit::DrawingAreaProxy::didSetSize): This now takes a LayerTreeContext parameter. * UIProcess/DrawingAreaProxy.messages.in: Add LayerTreeContext parameter. * UIProcess/DrawingAreaProxyImpl.cpp: Get rid of m_isInAcceleratedCompositingMode and use the current layer context instead. (WebKit::DrawingAreaProxyImpl::paint): Bail if the call to DidSetSize ended up entering accelerated compositing mode. (WebKit::DrawingAreaProxyImpl::didSetSize): If the new layer tree context is different, enter/exit accelerated compositing mode accordingly. (WebKit::DrawingAreaProxyImpl::enterAcceleratedCompositingMode): (WebKit::DrawingAreaProxyImpl::exitAcceleratedCompositingMode): Update the layer tree context. * UIProcess/DrawingAreaProxyImpl.h: (WebKit::DrawingAreaProxyImpl::isInAcceleratedCompositingMode): Add simple getter. * WebProcess/WebPage/DrawingAreaImpl.cpp: (WebKit::DrawingAreaImpl::setSize): Pass along the layer tree context. Canonical link: https://commits.webkit.org/67625@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@77546 268f45cc-cd09-0410-ab3c-d52691b4dbfc
- Loading branch information
Anders Carlsson
committed
Feb 3, 2011
1 parent
d5e84dc
commit 220e78d
Showing
8 changed files
with
94 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters