Add test case for mouseleave events within window bounds

Add test case for mouseleave events within window bounds

The test checks if the mouseout/mouseleave events are dispatched
to JS when the mouse leave event is triggered within the bounds
of the target window (eg. the window is being covered by some
other window).

BUG=450631
R=rbyers@chromium.org
TEST=fast/events/event-sender-mouseleave.html

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=191806

[Miyoung Shin(g), 2015-02-16 07:44:33]

This patch depends on http://crrev.com/928973002/.

[Miyoung Shin(g), 2015-03-06 07:35:01]

@Rick, PTAL. 
We can go the review step due to landing https://crrev.com/928973002/

[Rick Byers, 2015-03-06 16:05:37]

Thanks, looks good.  Just one suggestion to make it more clear what special case
you're covering (the common case of mouseleave due to the mouse actually leaving
the bounds of the element/window has always worked fine I believe).

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
File LayoutTests/fast/events/event-sender-mouseleave.html (right):

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
LayoutTests/fast/events/event-sender-mouseleave.html:20: description('Test that
a mouse leave event is triggered.');
nit add: "when the OS tells us the mouse has left without changing position"

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
LayoutTests/fast/events/event-sender-mouseleave.html:25: hasMouseLeave = true;
please verify here (and below if you like) that the mouse event co-ordinates are
still inside the box.  This worked fine in the past in the common case where the
co-ordinates were actually outside the box, but the bug was that if the
co-ordinates were still technically inside the box then we'd get only a
mousemove event - even though the OS is telling us the mouse isn't over our
window anymore.

eg. just:
 shouldBe('box.offsetLeft + 10', e.clientX)
 shouldBe('box.offsetTop + 10', e.clientY)
or something like that should be sufficient.

[Miyoung Shin(g), 2015-03-09 15:47:27]

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
File LayoutTests/fast/events/event-sender-mouseleave.html (right):

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
LayoutTests/fast/events/event-sender-mouseleave.html:20: description('Test that
a mouse leave event is triggered.');
On 2015/03/06 16:05:37, Rick Byers wrote:
> nit add: "when the OS tells us the mouse has left without changing position"

Done.

https://codereview.chromium.org/930803002/diff/20001/LayoutTests/fast/events/...
LayoutTests/fast/events/event-sender-mouseleave.html:25: hasMouseLeave = true;
On 2015/03/06 16:05:37, Rick Byers wrote:
> please verify here (and below if you like) that the mouse event co-ordinates
are
> still inside the box.  This worked fine in the past in the common case where
the
> co-ordinates were actually outside the box, but the bug was that if the
> co-ordinates were still technically inside the box then we'd get only a
> mousemove event - even though the OS is telling us the mouse isn't over our
> window anymore.
> 
> eg. just:
>  shouldBe('box.offsetLeft + 10', e.clientX)
>  shouldBe('box.offsetTop + 10', e.clientY)
> or something like that should be sufficient.

Done. Thank you for your comment.

[Rick Byers, 2015-03-12 16:49:05]

Thanks LGTM

[Miyoung Shin(g), 2015-03-13 00:05:06]

The CQ bit was checked by myid.o.shin@gmail.com

[commit-bot: I haz the power, 2015-03-13 00:05:27]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/930803002/40001

[commit-bot: I haz the power, 2015-03-13 01:32:13]

Committed patchset #3 (id:40001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=191806