| Summary: | Overview effect can have both keyboard and mouse hover highlight effects, and they look identical | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Jin Liu <ad.liu.jin> |
| Component: | effects-overview | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | dev.bacteriostat, nate |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.25.90 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | screencast of the bug | ||
|
Description
Jin Liu
2022-09-16 02:04:25 UTC
Created attachment 152089 [details]
screencast of the bug
Unable to reproduce. For me the cursor does not highlight anything which might be a bug on its own I guess. This is intentional, and in fact it's what we do in multiple other places. It's so your keyboard selection doesn't get lost if you use the mouse. If we changed this, then you would lose your keyboard selection when you moved the mouse, even accidentally. (In reply to Nate Graham from comment #3) > This is intentional, and in fact it's what we do in multiple other places. > It's so your keyboard selection doesn't get lost if you use the mouse. If we > changed this, then you would lose your keyboard selection when you moved the > mouse, even accidentally. But I don't see how the current behavior helps in that case: 1. If I use the keyboard arrow keys to highlight a window, then move the mouse in then out of that window, the selection is lost. 2. If I use the keyboard arrow keys to highlight a window, then move the mouse to another window, the selection is lost. 3. If I hover the mouse on one window, the use the keyboard arrow keys, there'll be two highlighted windows (one under the mouse, another keyboard selection), and it's confusing which one is really "selected". (the window not under the mouse is keyboard selection and will react to Enter key) (In reply to Jin Liu from comment #4) > (In reply to Nate Graham from comment #3) > > This is intentional, and in fact it's what we do in multiple other places. > > It's so your keyboard selection doesn't get lost if you use the mouse. If we > > changed this, then you would lose your keyboard selection when you moved the > > mouse, even accidentally. > > But I don't see how the current behavior helps in that case: > 1. If I use the keyboard arrow keys to highlight a window, then move the > mouse in then out of that window, the selection is lost. > 2. If I use the keyboard arrow keys to highlight a window, then move the > mouse to another window, the selection is lost. > 3. If I hover the mouse on one window, the use the keyboard arrow keys, > there'll be two highlighted windows (one under the mouse, another keyboard > selection), and it's confusing which one is really "selected". (the window > not under the mouse is keyboard selection and will react to Enter key) Point 1,2 are allright, but point 3 is especially confusing. Either the keyboard selection and the mouse hover are visually very different (as in Dolphin), or there's always one highlight (as in Kickoff). The highlights looking the same for both keyboard and mouse selection seems valid. Folder view is also like Dolphin, with two highlights but they look different. (In reply to Nate Graham from comment #6) > The highlights looking the same for both keyboard and mouse selection seems > valid. Folder view is also like Dolphin, with two highlights but they look > different. Yes. And in Folder View, mouse hover doesn't reset keyboard selection, while in Overview it does. However, I doubt that Folder View is a good model for Overview: 1. There are not that many windows on one screen. So perhaps keyboard selection accidentally reset by mouse isn't such a big thing, to warrent extra complexity of two types of highlight. 2. Overview doesn't support multiple selection like Folder View. With multiple selection, "selection" and "hover" must be distinct. Not the case for Overview. IMHO how Kickoff handles keyboard and mouse selections looks good enough in this case. |