Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(245)

Issue 11644035: cc: Invalidate the full tiled layer when contents scale changes. (Closed)

Created:
8 years ago by danakj
Modified:
8 years ago
CC:
chromium-reviews, cc-bugs_chromium.org, piman, backer
Visibility:
Public.

Description

cc: Invalidate the full tiled layer when contents scale changes. Previously we invalidated only the area outside of the previous bounds, but this is incorrect when changing the scale. The verifyInvalidationWhenContentsScaleChanges test was not actually testing to make sure invalidation happened, so fixed the test to do its job. Tests: TiledLayerTest.verifyInvalidationWhenContentsScaleChanges BUG=166715 R=enne NOTRY=true Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=174042

Patch Set 1 #

Total comments: 1

Patch Set 2 : #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+43 lines, -7 lines) Patch
M cc/contents_scaling_layer.h View 1 chunk +9 lines, -0 lines 0 comments Download
M cc/contents_scaling_layer.cc View 2 chunks +18 lines, -1 line 0 comments Download
M cc/layer_tree_host_unittest_animation.cc View 1 1 chunk +2 lines, -2 lines 0 comments Download
M cc/scrollbar_layer.cc View 1 1 chunk +3 lines, -1 line 0 comments Download
M cc/tiled_layer.cc View 1 chunk +3 lines, -0 lines 2 comments Download
M cc/tiled_layer_unittest.cc View 2 chunks +8 lines, -3 lines 0 comments Download

Messages

Total messages: 7 (0 generated)
danakj
8 years ago (2012-12-19 23:51:41 UTC) #1
enne (OOO)
lgtm https://codereview.chromium.org/11644035/diff/1/cc/tiled_layer.cc File cc/tiled_layer.cc (right): https://codereview.chromium.org/11644035/diff/1/cc/tiled_layer.cc#newcode637 cc/tiled_layer.cc:637: ContentsScalingLayer::update(queue, occlusion, stats); You should do this in ...
8 years ago (2012-12-19 23:57:24 UTC) #2
trchen
Confirmed. This fixes bug 166715
8 years ago (2012-12-19 23:59:56 UTC) #3
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/danakj@chromium.org/11644035/6001
8 years ago (2012-12-20 00:09:10 UTC) #4
commit-bot: I haz the power
Change committed as 174042
8 years ago (2012-12-20 00:09:32 UTC) #5
klobag.chromium
https://chromiumcodereview.appspot.com/11644035/diff/6001/cc/tiled_layer.cc File cc/tiled_layer.cc (right): https://chromiumcodereview.appspot.com/11644035/diff/6001/cc/tiled_layer.cc#newcode637 cc/tiled_layer.cc:637: ContentsScalingLayer::update(queue, occlusion, stats); Should this be after updateBounds()?
8 years ago (2012-12-20 00:40:58 UTC) #6
danakj
8 years ago (2012-12-20 00:52:28 UTC) #7
Message was sent while issue was closed.
https://chromiumcodereview.appspot.com/11644035/diff/6001/cc/tiled_layer.cc
File cc/tiled_layer.cc (right):

https://chromiumcodereview.appspot.com/11644035/diff/6001/cc/tiled_layer.cc#n...
cc/tiled_layer.cc:637: ContentsScalingLayer::update(queue, occlusion, stats);
On 2012/12/20 00:40:58, klobag.chromium wrote:
> Should this be after updateBounds()?

This is acting as the ContentsScalingLayer's version of updating. Other layers
than tiled layer (eg scrolbar) also inherit from ContentsScalingLayer, and they
should call its update() and have it do the same thing.

Whereas updateBounds() is a TiledLayer specific thing.

Powered by Google App Engine
This is Rietveld 408576698