From 659490b7dd2c6092e85a1724a23ebb79f6e081d9 Mon Sep 17 00:00:00 2001 From: Alexandru Croitor Date: Mon, 21 Dec 2015 17:08:57 +0100 Subject: Fix MouseMove event handling when opening a new tab with middle click. When opening a new tab by middle clicking on a link in a web page, two MouseMove events are sent to Chromium consecutively, without getting proper acknowledgment events, which causes further move events not to be handled properly. Fix consists in preventing the second move event from being sent. Change-Id: Ia0a64698476226e472faa53f75b51dfb6ed477c9 Task-number: QTBUG-50031 Reviewed-by: Joerg Bornemann --- src/core/render_widget_host_view_qt.cpp | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/core/render_widget_host_view_qt.cpp') diff --git a/src/core/render_widget_host_view_qt.cpp b/src/core/render_widget_host_view_qt.cpp index 7c5ed64e7..e4770cc72 100644 --- a/src/core/render_widget_host_view_qt.cpp +++ b/src/core/render_widget_host_view_qt.cpp @@ -747,6 +747,10 @@ bool RenderWidgetHostViewQt::forwardEvent(QEvent *event) Focus(); // Fall through. case QEvent::MouseButtonRelease: case QEvent::MouseMove: + // Skip second MouseMove event when a window is being adopted, so that Chromium + // can properly handle further move events. + if (m_adapterClient->isBeingAdopted()) + return false; handleMouseEvent(static_cast(event)); break; case QEvent::KeyPress: -- cgit v1.2.3