Bug 447261 - Dropdowns do not respond to hold-and-drag
Summary: Dropdowns do not respond to hold-and-drag
Status: RESOLVED DUPLICATE of bug 439734
Alias: None
Product: frameworks-qqc2-desktop-style
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.90.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-20 09:36 UTC by strangequark
Modified: 2022-01-11 22:40 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description strangequark 2021-12-20 09:36:03 UTC
SUMMARY
The dropdowns in multiple places (eg Kalendar's menubars, System Settings' configure hamburger menu, etc) do not respond to holding them and dragging them, which virtually every KDE app used to respond to.


STEPS TO REPRODUCE
1. Go to Kalendar's menubar or System Settings' configure hamburger menu, and click on it with a mouse but don't let go of the click
2. Do the same in any other app (eg Kate/Okular menubars)

OBSERVED RESULT
Nothing happens with System Settings or Kalendar, but when doing the same with Kate/Okular the dropdown pops up.

EXPECTED RESULT
Same thing should happen with all the apps.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Graphics Platform: X11

ADDITIONAL INFORMATION
I'm not sure if this is the right category to file this bug, I'm sorry if I filed it in the wrong place. I'm also not sure if it's a matter of implementation or a problem with the underlying thing, so I'm sorry if these bugs should have been filed with the invidual apps instead.
Comment 1 Nate Graham 2022-01-11 22:28:39 UTC
Similar issue as Bug 439735.
Comment 2 Janet Blackquill 2022-01-11 22:39:17 UTC
This is a (much better worded) duplicate of bug 439734; this behaviour is also menu rolling.
Comment 3 Nate Graham 2022-01-11 22:40:04 UTC

*** This bug has been marked as a duplicate of bug 439734 ***