cdcf00390c
Commit 353ce5344fbde5a6cecbdd2c131e1cf0f4b7f383 made QMenu::exec() return immediately (without showing the menu), which meant it never emitted aboutToHide() and QToolButton didn't reset mouseButtonDown. Therefore, on the next click on the toolbutton (maybe by then the menu has actions), it won't even try to show it (because mouseButtonDown is still true). Task-number: QTBUG-129108 Change-Id: I3f84b9a35eb444fc33d8516c4be130293c04017d Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit f0508b7ff3d2393521f49dcb1a9e880bf7665a87) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit 05016926ae37ae73a9da9375a95f3a4e8234477e) |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.