| Summary: | Open applications via mouse scroll wheel | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | evea <kde> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | fanzhuyifan, nate, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=461481 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
evea
2024-08-12 01:09:27 UTC
But why? What's the UX benefit of this? Why not just click? This is one of the additions I would suggest getting a consistent workflow. For newcomers, currently scrolling on applications will give you an unpredictable behavior. For example, the user sees a Firefox icon, scroll on it, and will be shown Dolphin, then kate, etc. The goal is to always know what will happen. Scrolling on an application should only ever show you the application you are scrolling over. This report extends this, by even launching the application. So when a user scrolls on Firefox, the user will always _only_ see Firefox pop up, not matter if multiple windows are open, only one window is open, or no window is open. Personally, I only put this on "scroll up", to circumvent misplacements of the mouse when scrolling through a neighboring application. (In reply to evea from comment #2) > This is one of the additions I would suggest getting a consistent workflow. > For newcomers, currently scrolling on applications will give you an > unpredictable behavior. For example, the user sees a Firefox icon, scroll on > it, and will be shown Dolphin, then kate, etc. IMHO this reduces consistency -- previously scrolling only brings up existing windows, but this creates new windows, which is really different. I think whether you view the current behavior as consistent or inconsistent depends very much on how you conceptualize what a scroll does. The intended design here is that scrolling over any part of the Task Manager switches between all of its items, no matter which one the pointer happened to be hovering over. In other words, it has the UX of a tab bar in an app, which behaves in the same way. The folks who get confused by this seem to be fixating on the fact that you're scrolling on a specific task, and not necessarily manipulating that exact task. We've had a number of requests for this exact same thing over the years; maybe it's time to make the scroll behavior conditional and switch between these two modes. But I'm curious, for those of you who want to scroll up on a task to un-minimize it, bring it to the front, or launch it (based on what its current state is), where is this desire coming from? Enough people request it that I feel like it must be migrated from some other UI that people are familiar with when they switch to Plasma or something. Can anyone clarify? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |