Fix mouse wheel over-scrolls when display is scaled and scroll is paginated

third_party/WebKit/LayoutTests/TestExpectations

Index: third_party/WebKit/LayoutTests/TestExpectations
diff --git a/third_party/WebKit/LayoutTests/TestExpectations b/third_party/WebKit/LayoutTests/TestExpectations
index 3c931727afe29294cd61bbb827b457bf1b65afbe..57f67a14f4e6932a03785aebb6df40ae8740b9a1 100644
--- a/third_party/WebKit/LayoutTests/TestExpectations
+++ b/third_party/WebKit/LayoutTests/TestExpectations
@@ -858,6 +858,9 @@ crbug.com/567837 virtual/scalefactor200/fast/hidpi/static/gesture-scroll-amount.
 crbug.com/567837 virtual/scalefactor150/fast/hidpi/static/mousewheel-scroll-amount.html [ Skip ]
 crbug.com/567837 virtual/scalefactor150/fast/hidpi/static/gesture-scroll-amount.html [ Skip ]
 
+crbug.com/666133 virtual/scalefactor200withzoom/fast/hidpi/static/gesture-scroll-amount.html [ NeedsRebaseline ]

[aelias_OOO_until_Jul13, 2017/02/16 22:11:13]

It doesn't make sense that this test result would have changed.  It's clearly
intended to scroll by pixel amounts.  It must be a preexisting problem with the
test that deltaHintUnits is incorrect set to Page.  Instead of changing the
expectations to be wrong, please change the event sender framework to set
deltaHintUnits by pixel.

[chengx, 2017/02/17 08:26:02]

Acknowledged.

+crbug.com/666133 virtual/scalefactor200withzoom/fast/hidpi/static/mousewheel-scroll-amount.html [ NeedsRebaseline ]

[aelias_OOO_until_Jul13, 2017/02/16 22:11:13]

Since these don't have any image expectations, please directly include the
rebaselined result in this patch instead of relying on rebaseline bot.  This
makes it easier to examine what changed and also simplifies
cherry-picks/reverts.  (Although, I suspect there shouldn't be any result
changes needed at all if the test framework is changed to configure the events
properly by pixel.O)

[chengx, 2017/02/17 08:26:02]

Acknowledged.

+
 # TODO(ojan): These tests aren't flaky. See crbug.com/517144.
 # Release trybots run asserts, but the main waterfall ones don't. So, even
 # though this is a non-flaky assert failure, we need to mark it [ Pass Crash ].