Fixing tile grid size used by cc:Picture to make it respect current tile configuration

cc/tiling_data.cc

 // Copyright 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/tiling_data.h"
 
 #include <algorithm>
 
 #include "ui/gfx/rect.h"
 #include "ui/gfx/vector2d.h"
@@ skipping 238 matching lines @@
   int top = (!y_index || num_tiles_y_ == 1) ? 0 : border_texels_;
 
   return gfx::Vector2d(left, top);
 }
 
 void TilingData::RecomputeNumTiles() {
   num_tiles_x_ = ComputeNumTiles(max_texture_size_.width(), total_size_.width(), border_texels_);
   num_tiles_y_ = ComputeNumTiles(max_texture_size_.height(), total_size_.height(), border_texels_);
 }
 
+gfx::Size TilingData::TileStride() const {
+  gfx::Size tile_grid_size = max_texture_size_;
+  tile_grid_size.Enlarge(- 2 * border_texels_, - 2 * border_texels_);

[danakj, 2013/02/11 17:12:46]

Does the TileGrid assume border pixels are on the outside of the grid squares or
on the inside of them like TilingData does?

+  return tile_grid_size;
+}
+
 TilingData::BaseIterator::BaseIterator(const TilingData* tiling_data)
     : tiling_data_(tiling_data),
       index_x_(-1),
       index_y_(-1) {
 }
 
 TilingData::Iterator::Iterator(const TilingData* tiling_data, gfx::Rect rect)
     : BaseIterator(tiling_data),
       left_(-1),
       right_(-1),
@@ skipping 120 matching lines @@
     }
 
     if (index_y_ > consider_bottom_)
       done();
   }
 
   return *this;
 }
 
 }  // namespace cc