commit | 9480b4c29caad4f4bd070e35111d9a03e53a3337 | [log] [tgz] |
---|---|---|
author | simon.fraser@apple.com <simon.fraser@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed May 22 00:12:49 2019 +0000 |
committer | simon.fraser@apple.com <simon.fraser@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed May 22 00:12:49 2019 +0000 |
tree | 8c941e2e3d3582bf7aea8f0d383325a3725941a1 | |
parent | 058b39402984831eed74663d6ad6d576aa5a3086 [diff] |
Layer flashing and poor perf during scrolling of message list on gmail.com and hotmail.com - overlap testing needs to constrained to clipping scopes https://bugs.webkit.org/show_bug.cgi?id=198091 <rdar://problem/49403082> Reviewed by Antti Koivisto. Source/WebCore: When overflow:scroll is scrolled asynchronously, we need to have already created compositing layers where necessary for clipped-out layers in the scrolled content so that we have something to reveal. We also have ensure that layers inside the scroller (but scrolled out of view) don't trigger overlap with layers outside the scroller. All this has to work when the containing block hierarchy (clipping/scrolling) doesn't match the paint order hierarchy (structure of the z-order and compositing trees). Overlap testing previously simply used a list of rectangles per compositing container (OverlapMapContainer). This is a series of layer bounds, built up as we traver the layer tree in z-order. Layers contribute to container N-2, and test against container N-1. To handle overlap with non-stacking-context scrollers, introduce the concept of a ClippingScope, which encompasses a set of layers sharing the same composited-scrolling containing-block ancestor. Within a ClippingScope, layer bounds are computed unclipped. Between them, bounds are tested clipped. Conceptually, each OverlapMapContainer has a tree of ClippingScopes (reflecting the containing-block order tree of composited overflow scroll), and rects are added to the appropriate ClippingScope. This tree is currently always root-relative; the root node is the RenderView's RenderLayer, and will accumulate the bounds of layers not inside composited overflow scroll (just like the old code). When a OverlapMapContainer is popped, the list of rectangles in its ClippingScope tree is merged with that of the previous container. Tests: compositing/layer-creation/clipping-scope/nested-scroller-overlap.html compositing/layer-creation/clipping-scope/overlap-constrained-inside-scroller.html compositing/layer-creation/clipping-scope/overlap-constrained-inside-stacking-context-scroller.html compositing/layer-creation/clipping-scope/scroller-with-negative-z-children.html compositing/layer-creation/clipping-scope/shared-layers-in-scroller.html * rendering/LayerOverlapMap.cpp: (WebCore::operator<<): (WebCore::OverlapMapContainer::OverlapMapContainer): (WebCore::OverlapMapContainer::ClippingScope::ClippingScope): (WebCore::OverlapMapContainer::ClippingScope::childWithLayer const): (WebCore::OverlapMapContainer::ClippingScope::addChildWithLayerAndBounds): (WebCore::OverlapMapContainer::ClippingScope::addChild): (WebCore::OverlapMapContainer::ClippingScope::appendRect): (WebCore::OverlapMapContainer::clippingScopeContainingLayerChildRecursive): (WebCore::OverlapMapContainer::scopeContainingLayer const): (WebCore::OverlapMapContainer::rootScope const): (WebCore::OverlapMapContainer::rootScope): (WebCore::OverlapMapContainer::add): (WebCore::OverlapMapContainer::overlapsLayers const): (WebCore::OverlapMapContainer::mergeClippingScopesRecursive): (WebCore::OverlapMapContainer::append): (WebCore::OverlapMapContainer::ensureClippingScopeForLayers): (WebCore::OverlapMapContainer::findClippingScopeForLayers const): (WebCore::OverlapMapContainer::recursiveOutputToStream const): (WebCore::OverlapMapContainer::dump const): (WebCore::LayerOverlapMap::LayerOverlapMap): (WebCore::LayerOverlapMap::add): (WebCore::LayerOverlapMap::overlapsLayers const): (WebCore::LayerOverlapMap::pushCompositingContainer): (WebCore::LayerOverlapMap::popCompositingContainer): (WebCore::OverlapMapContainer::unite): Deleted. (WebCore::OverlapMapContainer::rectList const): Deleted. * rendering/LayerOverlapMap.h: * rendering/RenderLayerCompositor.cpp: (WebCore::RenderLayerCompositor::BackingSharingState::appendSharingLayer): (WebCore::RenderLayerCompositor::BackingSharingState::updateBeforeDescendantTraversal): (WebCore::RenderLayerCompositor::updateCompositingLayers): (WebCore::RenderLayerCompositor::computeCompositingRequirements): (WebCore::RenderLayerCompositor::traverseUnchangedSubtree): (WebCore::RenderLayerCompositor::computeExtent const): (WebCore::createsClippingScope): (WebCore::enclosingClippingScopes): (WebCore::RenderLayerCompositor::addToOverlapMap const): (WebCore::RenderLayerCompositor::updateOverlapMap const): (WebCore::RenderLayerCompositor::layerOverlaps const): * rendering/RenderLayerCompositor.h: Source/WebCore/../../LayoutTests: * TestExpectations: * compositing/layer-creation/clipping-scope/nested-scroller-overlap-expected.txt: Added. * compositing/layer-creation/clipping-scope/nested-scroller-overlap.html: Added. * compositing/layer-creation/clipping-scope/overlap-constrained-inside-scroller-expected.txt: Added. * compositing/layer-creation/clipping-scope/overlap-constrained-inside-scroller.html: Added. * compositing/layer-creation/clipping-scope/overlap-constrained-inside-stacking-context-scroller-expected.txt: Added. * compositing/layer-creation/clipping-scope/overlap-constrained-inside-stacking-context-scroller.html: Added. * compositing/layer-creation/clipping-scope/scroller-with-negative-z-children-expected.txt: Added. * compositing/layer-creation/clipping-scope/scroller-with-negative-z-children.html: Added. * compositing/layer-creation/clipping-scope/shared-layers-in-scroller-expected.txt: Added. * compositing/layer-creation/clipping-scope/shared-layers-in-scroller.html: Added. * platform/ios-wk2/TestExpectations: * platform/ios-wk2/compositing/layer-creation/clipping-scope/nested-scroller-overlap-expected.txt: Added. * platform/ios-wk2/compositing/layer-creation/clipping-scope/overlap-constrained-inside-scroller-expected.txt: Added. * platform/ios-wk2/compositing/layer-creation/clipping-scope/overlap-constrained-inside-stacking-context-scroller-expected.txt: Added. * platform/ios-wk2/compositing/layer-creation/clipping-scope/scroller-with-negative-z-children-expected.txt: Added. * platform/ios-wk2/compositing/layer-creation/clipping-scope/shared-layers-in-scroller-expected.txt: Added. * platform/mac-wk2/TestExpectations: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@245602 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
or
git clone https://git.webkit.org/git/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.