Use IntRect instead of FloatRect for window positions and sizes

LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html

Index: LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html
diff --git a/LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html b/LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html
index 28f6876616b709ac1c5118f9bf6ade93542ba666..01693ef4713335994e3ec1924b39022b621f8fab 100644
--- a/LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html
+++ b/LayoutTests/fast/dom/Window/window-resize-and-move-arguments.html
@@ -17,7 +17,7 @@
 
     function reset()
     {
-        window.moveTo(0, 0);
+        window.moveTo(screen.availLeft + 100, screen.availTop + 100);

[Jens Widell, 2015/01/28 12:29:55]

This whole test was somewhat confusing.

In my environment (I have multiple monitors) the screen's top left corner was at
x=1200, y=240. So moveTo(0, 0) was really moveTo(1200, 240). And below, the test
asserts that moveTo() moves the window to screen.avail{Left,Top}. But it didn't
(and doesn't): moveTo() without arguments doesn't move the window at all.

Resetting the window here away move a "zero" position means the test now
actually sees a difference between "moving to 0, 0" and "not moving", which it
previously didn't.

         window.resizeTo(300, 200);
         resetWidth = window.outerWidth;
         resetHeight = window.outerHeight;
@@ -87,14 +87,14 @@
 
     debug("Testing - moveTo with 0 arguments");
     window.moveTo();
-    shouldBe('window.screenX', 'screen.availLeft');
-    shouldBe('window.screenY', 'screen.availTop');
+    shouldBe('window.screenX', 'resetX');
+    shouldBe('window.screenY', 'resetY');
     reset();
 
     debug("Testing - moveTo with 1 argument");
     window.moveTo(x);
     shouldBe('window.screenX', 'Math.max(x, screen.availLeft)');
-    shouldBe('window.screenY', 'screen.availTop');
+    shouldBe('window.screenY', 'resetY');
     reset();
 
     debug("Testing - moveTo with more than 2 arguments");