Fix incorrectly dropping WM_MOUSELEAVE after a call to SetCapture
After fixing the bounds check in r623087 it could happen that the window below the mouse is still the render_widget_host after a tooltip was created and called SetCapture to not forward mouse events to us. This makes sure that we only do the bounds check if there is not a capture currently active. R=kenrb@chromium.org, lanwei@chromium.org Bug: 944772 Change-Id: Id6f5ab4ca1f643a8830ad22b36a6975b1da5bc95 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554356Reviewed-by:Scott Violet <sky@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Lan Wei <lanwei@chromium.org> Cr-Commit-Position: refs/heads/master@{#649615}
Showing
Please register or sign in to comment