Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-44400

QPushButton remains in hover state after menu closed

    XMLWordPrintable

Details

    • macOS

    Description

      QPushButton remains in the hovered state after the menu has closed by mouse click outside of menu and button areas.

      Steps to reproduce :
      Run qtbug44400.zip which uses attached main.cpp
      The button's background color is red (default) and white (hovered)
      Click on button, then click on parent widget or the menu.

      Expected result
      Button's background color becomes red

      Actual result
      Button background remains white (i.e. hovered state)

      This problem doesn't seem to occur on Windows

      Attachments

        1. main.cpp
          0.6 kB
        2. qtbug44400.zip
          1 kB

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-78970 REG 5.9.4 => 5.12.4 setAutoRaise not working on Mac

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-49395 Problem with QToolButton hover state on MacOSX after hiding dialog with it

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-78970 REG 5.9.4 => 5.12.4 setAutoRaise not working on Mac

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              vhilshei Volker Hilsheimer
              amd00 Andrey Dudakov
              Veli-Pekka Heinonen Veli-Pekka Heinonen
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: