summaryrefslogtreecommitdiffstats
path: root/examples/webenginequick/lifecycle/CMakeLists.txt
diff options
context:
space:
mode:
authorAnu Aliyas <anu.aliyas@qt.io>2024-02-05 14:10:03 +0100
committerQt Cherry-pick Bot <cherrypick_bot@qt-project.org>2024-06-01 00:26:49 +0000
commit6794e5bdacc0324aea25b323268e126ab634eafc (patch)
tree5b2f92ac26f37386a3f8b13d0c1034b91ad4eb26 /examples/webenginequick/lifecycle/CMakeLists.txt
parentfb3ad55c39290229e0d211b40443155e23312bdb (diff)
Reset wheel_widget when forwarding unhandled mouse event6.7
If QApplicationPrivate::wheel_widget is present all wheel events are forwarded to the wheel widget. If the wheel widget doesn't handle the event, it is forwarded to the parent widget. With QtWebEngine in the picture, all the mouse wheel events are forwarded to Chromium. If Chromium doesn't handle the event, QtWebEngine will send the unhandled mouse wheel event to the parent using qApp->sendEvent(). This operation is performed asynchronously. There is no immediate way to determine whether QtWebEngine is going to handle the event. If QApplicationPrivate::wheel_widget is not null, the mouse wheel handling logic will forward the unhandled event back to the wheel_widget which is QtWebEngine in this case leading to QtWebEngine grabbing all mouse wheel events. Also there is no way to get proper phase information from the Chromium, and the unhandled events are forwarded with Qt::NoScrollPhase. QApplicationPrivate::wheel_widget is set to nullptr to avoid the crash. Fixes: QTBUG-121359 Pick-to: 6.6 6.5 Change-Id: I01fef5605c264fdc97df041d57dc3589aa17c49f Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> (cherry picked from commit 9f247e3067113bc47b5e2635bc0b4dc69f8289f3) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Diffstat (limited to 'examples/webenginequick/lifecycle/CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions