Bug 370465 - Window state is hard to tell by looking at the task manager button; consider using different background colors for more states
Summary: Window state is hard to tell by looking at the task manager button; consider ...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.8.0
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords: usability
: 164218 350356 375684 384290 405602 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-10-11 13:48 UTC by Flupp
Modified: 2021-07-18 14:49 UTC (History)
16 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.66
Sentry Crash Report:
nate: Usability+
hein: VisualDesign+


Attachments
different window/button states (36.93 KB, image/png)
2016-10-11 13:50 UTC, Flupp
Details
different window/button states with plasma-workspace 5.8.3 (36.04 KB, image/png)
2016-11-03 12:39 UTC, Flupp
Details
Crude mockup of proposed changes (move to colored backgrounds for everything) (30.95 KB, image/png)
2017-10-16 03:30 UTC, Nate Graham
Details
New vs old theme: in new can't distinguish focused window (dolphin) (156.87 KB, image/png)
2020-02-28 15:38 UTC, Michael D
Details
different window/button states with plasma-workspace 5.22.3 (57.20 KB, application/x-troff-man)
2021-07-18 14:45 UTC, Flupp
Details
different window/button states with plasma-workspace 5.22.3 (57.20 KB, image/png)
2021-07-18 14:49 UTC, Flupp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Flupp 2016-10-11 13:48:04 UTC
I am not sure, if this is an issue of the task manager plasmoid, the plasma theme (currently, I am using Breeze), or both.

I find it rather difficult to tell the state of a window just by looking at its task manager button. Consider the following visual representations:

* a hovered button has a blue background color and a glowing icon,
* the button of the active window has a blue background color,
* the buttons of non-minimized windows have a light gray background color,
* the buttons of minimized windows have a dark gray background color.

I have the following problems:

* A hovered button always has the same visual representation, disregarding the state of the window completely. This implies, that the visual representation does not change after clicking the button, while the actual state of the window does change. I often click task bar buttons repeatedly, because I do not see a change of the button and the related window is in another corner of another monitor and therefore out of my field of view.
* It is not intuitively clear to me, that a dark gray button represents a minimized window. Especially, if there is exactly one minimized window and no active window.

Reproducible: Always



Expected Results:  
The state of a window should always be intuitively represented by the task manager button, especially while hovering a button.

I suggest, to indicate hovering only by glowing (maybe including the text). In this way, the state of the window stays visible.

For minimized windows I suggest to dim the text and maybe also the icon, similar to disabled GUI elements.
Comment 1 Flupp 2016-10-11 13:50:12 UTC
Created attachment 101527 [details]
different window/button states

A screenshot of the different window/button states in the same order as listed above.
Comment 2 Eike Hein 2016-10-11 14:17:07 UTC
VDG needs to look at it.
Comment 3 Flupp 2016-11-03 12:39:21 UTC
Created attachment 101999 [details]
different window/button states with plasma-workspace 5.8.3

In the current version (plasma-workspace 5.8.3), the distinction between hovered and active buttons is better in my opinion. Yet, the problems that I stated in comment 0 still persist. I would even argue that minimized tasks now stand out even more.
Comment 4 David Edmundson 2016-11-04 23:18:52 UTC
*** Bug 350356 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2017-10-16 03:18:23 UTC
*** Bug 384290 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2017-10-16 03:30:45 UTC
Created attachment 108368 [details]
Crude mockup of proposed changes (move to colored backgrounds for everything)

Proposal:

- A colored square behind the running and active program gets a background color equal to "Selection Background" from the color theme
- A colored square behind running but inactive programs gets a background color equal to "Alternate Background" from the color theme
- A colored square behind minimized programs gets a background color equal to "Alternate Background" from the color theme, but darkened.

Crude mockup attached.
Comment 7 Andres Betts 2018-04-02 19:12:28 UTC
I would be in favor of something like the proposed change. However, we have to discuss colors at some point.
Comment 8 Kai Uwe Broulik 2018-04-03 07:51:10 UTC
> A colored square behind the running and active program gets a background color equal to "Selection Background" from the color theme

We had exactly what you suggest for a while and then it was changed back to line art. Can we stop randomly changing theme whenever someone comes by and doesn't like something unless it actually comes enclosed with a 20 page empirical study made in a lab or something?
Comment 9 Nate Graham 2018-04-03 13:45:42 UTC
(In reply to Kai Uwe Broulik from comment #8)
> > A colored square behind the running and active program gets a background color equal to "Selection Background" from the color theme
> 
> We had exactly what you suggest for a while and then it was changed back to
> line art. Can we stop randomly changing theme whenever someone comes by and
> doesn't like something unless it actually comes enclosed with a 20 page
> empirical study made in a lab or something?

For me it is not personal preference; it's a matter of usability and visual communication:
- Using a thin gray or blue line to denote what's running and active (respectively) is challenging to visually distinguish at a glance.
- Because a different background color is already used for minimized windows/apps, not doing the same for running or active windows/apps visually communicates to the user that it's more important to be able to tell when a window or app is minimized than it is to tell when it's running or that it's the active window, which seems odd.

Given that we already had the requested design in the past, I'd be interested in knowing why it was changed to the current design. If the reason was because the visual designers wanted it to look more "modern", "flat", "minimalistic", or "material", then I would suggest that the onus should have been on *them* to include the requested 20-page lab study. :)
Comment 10 Nate Graham 2018-12-07 17:59:11 UTC
*** Bug 164218 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2019-12-06 18:19:05 UTC
*** Bug 375684 has been marked as a duplicate of this bug. ***
Comment 12 Nate Graham 2019-12-06 18:31:57 UTC
*** Bug 405602 has been marked as a duplicate of this bug. ***
Comment 13 Nate Graham 2019-12-06 18:33:21 UTC
We've got an open patch that will fix this: https://phabricator.kde.org/D25340
Comment 14 Nate Graham 2019-12-06 19:37:13 UTC
FWIW this isn't a Task Manager bug, it's a Breeze Plasma theme bug.
Comment 15 Noah Davis 2019-12-09 18:00:58 UTC
Git commit 7e52c869de2d58ff714b60252041a447db2c10c0 by Noah Davis.
Committed on 09/12/2019 at 18:00.
Pushed by ndavis into branch 'master'.

Added background colors to active and inactive icon view

Summary:
Added:
- Semi-transparent blue background color for active window
- Semi-transparent gray background color for inactive but not minimized window

Changed:
- Reduced opacity for minimized background
FIXED-IN: 5.66

Test Plan:
Before:
{F7804957}
After:
{F7805236}

Reviewers: #vdg, ngraham, niccolove

Reviewed By: #vdg, ngraham

Subscribers: filipf, manueljlin, ngraham, ndavis, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D25340

M  +976  -4784 src/desktoptheme/breeze/widgets/tasks.svg

https://commits.kde.org/plasma-framework/7e52c869de2d58ff714b60252041a447db2c10c0
Comment 16 Michael D 2020-02-28 15:37:36 UTC
I know this is already marked as fixed, however, with the recent changes, I find it harder to distinguish the focused window from the others when using certain color schemes. I've attached a screenshot showing the difference between old and new Breeze theme using the Norway color scheme. With the new changes it is virtually impossible to distinguish the focused window (dolphin). With the old theme, it's much easier to distinguish it. I haven't tested other color schemes except the default Breeze one where the recent changes actually help rather than hurt.

Is there a fix that might help no matter the color scheme?
Comment 17 Michael D 2020-02-28 15:38:31 UTC
Created attachment 126482 [details]
New vs old theme: in new can't distinguish focused window (dolphin)

Norway color scheme used
Comment 18 Nate Graham 2020-02-29 02:21:29 UTC
It's a bug in the Norway color scheme. Whenever you change anything, you find all kinds of bugs in the customization options. :)
Comment 19 Flupp 2021-07-18 14:45:21 UTC
Created attachment 140163 [details]
different window/button states with plasma-workspace 5.22.3

With the patch from 2019-12-09, which (also) uses the background color for representing the window state, the situation got much better. Thanks!

However, an important issues I initially mentioned still remains:

“
* A hovered button always has the same visual representation, disregarding the state of the window completely. This implies, that the visual representation does not change after clicking the button, while the actual state of the window does change. I often click task bar buttons repeatedly, because I do not see a change of the button and the related window is in another corner of another monitor and therefore out of my field of view.
”

I am not sure if I shall reopen this issue or create another issue for that.
Comment 20 Flupp 2021-07-18 14:49:17 UTC
Created attachment 140164 [details]
different window/button states with plasma-workspace 5.22.3

(Upload image again with correct MIME type.)