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

Side by Side Diff: cc/damage_tracker.cc

Issue 11410021: Remove WTF and WebCore from cc/ and webkit/compositor_bindings/ (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: fix content_browsertests Created 8 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « cc/contents_scaling_layer_unittest.cc ('k') | cc/damage_tracker_unittest.cc » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 // Copyright 2011 The Chromium Authors. All rights reserved. 1 // Copyright 2011 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 #include "config.h"
6
7 #include "cc/damage_tracker.h" 5 #include "cc/damage_tracker.h"
8 6
9 #include "cc/layer_impl.h" 7 #include "cc/layer_impl.h"
10 #include "cc/layer_tree_host_common.h" 8 #include "cc/layer_tree_host_common.h"
11 #include "cc/math_util.h" 9 #include "cc/math_util.h"
12 #include "cc/render_surface_impl.h" 10 #include "cc/render_surface_impl.h"
13 #include <public/WebFilterOperations.h> 11 #include <public/WebFilterOperations.h>
14 12
15 using WebKit::WebTransformationMatrix; 13 using WebKit::WebTransformationMatrix;
16 14
(...skipping 319 matching lines...) Expand 10 before | Expand all | Expand 10 after
336 334
337 // If the layer has a background filter, this may cause pixels in our surfac e to be expanded, so we will need to expand any damage 335 // If the layer has a background filter, this may cause pixels in our surfac e to be expanded, so we will need to expand any damage
338 // at or below this layer. We expand the damage from this layer too, as we n eed to readback those pixels from the surface with only 336 // at or below this layer. We expand the damage from this layer too, as we n eed to readback those pixels from the surface with only
339 // the contents of layers below this one in them. This means we need to redr aw any pixels in the surface being used for the blur in 337 // the contents of layers below this one in them. This means we need to redr aw any pixels in the surface being used for the blur in
340 // this layer this frame. 338 // this layer this frame.
341 if (layer->backgroundFilters().hasFilterThatMovesPixels()) 339 if (layer->backgroundFilters().hasFilterThatMovesPixels())
342 expandDamageRectInsideRectWithFilters(targetDamageRect, surfaceRectInTar getSpace, layer->backgroundFilters()); 340 expandDamageRectInsideRectWithFilters(targetDamageRect, surfaceRectInTar getSpace, layer->backgroundFilters());
343 } 341 }
344 342
345 } // namespace cc 343 } // namespace cc
346
OLDNEW
« no previous file with comments | « cc/contents_scaling_layer_unittest.cc ('k') | cc/damage_tracker_unittest.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698