Remove most remaining references to IntRect and FloatRect.

The remaining uses are:
- Dealing with the output of Region::rects() which gives a vector of
  WebCore::IntRects.
- Using FloatRect::isExpressibleAsIntRect.

Covered by existing tests; no new behaviour.

BUG=147395
R=enne

Review URL: https://codereview.chromium.org/11275113

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165542 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 1 deletions

diff --git a/cc/layer_tiling_data.cc b/cc/layer_tiling_data.cc
index b3ba58d..10086da 100644
--- a/cc/layer_tiling_data.cc
+++ b/cc/layer_tiling_data.cc
@@ -7,6 +7,8 @@
 
 #include "cc/layer_tiling_data.h"
 
+#include "IntRect.h"
+#include "IntSize.h"
 #include "base/logging.h"
 
 using namespace std;
@@ -117,7 +119,7 @@ Region LayerTilingData::opaqueRegionInContentRect(const gfx::Rect& contentRect)
                 continue;
 
             gfx::Rect tileOpaqueRect = gfx::IntersectRects(contentRect, tile->opaqueRect());
-            opaqueRegion.unite(cc::IntRect(tileOpaqueRect));
+            opaqueRegion.Union(tileOpaqueRect);
         }
     }
     return opaqueRegion;