commit | a6932efa7fe2d15fe79bb5efb0b65bc738a6ec8e | [log] [tgz] |
---|---|---|
author | Xianzhu Wang <wangxianzhu@chromium.org> | Tue Oct 27 23:52:09 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Oct 27 23:52:09 2020 |
tree | 777d3d0a21f24bc5cd0b9306e0a46526a1c052ba | |
parent | cd8108c5d75f76fda54650cd4c5726fd14e48af3 [diff] |
Revert "Remove GraphicsLayer::SetNeedsDisplay()" This reverts commit 80a372d91c63d6da3471206cec49027b72a61e6f. Reason for revert: To diagnose performance regressions. Original change's description: > Remove GraphicsLayer::SetNeedsDisplay() > > With unified PaintController, to support SetNeedsDisplay() we would > need to add PaintController mechanism to invalidate all display items > in a range for a GraphicsLayer. Removing SetNeedsDisplay() can avoid > that. We instead use the normal paint invalidation code path. For > needed invalidation, now invalidate the display items of and in the > GraphicsLayer. Some invalidations are not needed because we have > already invalidated the DisplayItemClients. > > Also rename SetContentsNeedsDisplay() to InvalidateContents(), and > SetNeedsDisplayInrect() to InvaldiateRaster() which is only called by > RasterInvalidator. > > Bug: 1132717 > Change-Id: I535cdcc7ee1d07e23a490fdf2aa267573a54d0ba > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2478026 > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> > Reviewed-by: Philip Rogers <pdr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#818673} TBR=wangxianzhu@chromium.org,pdr@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1132717, 1140634 Change-Id: Ife45cc8b39b6aac762f228d80634a33b6b4889b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503322 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#821505}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.