| Summary: | Using the icon specified by the app's desktop file can cause a mismatch between the icon provided by the window itself which is visible in the Task Manager | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Michal Kec (MiK) <KDE> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.21.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Application task bar: Three different windows, three identical icons
Task switcher: Three different windows, three different (correct) icons |
||
|
Description
Michal Kec (MiK)
2021-02-20 11:10:21 UTC
Created attachment 135959 [details]
Task switcher: Three different windows, three different (correct) icons
The Task Manager uses the icon specified in the app's .desktop file. The Task Switcher asks the window itself for what its icon should be. Arguably, the non-Icons-Only Task Manager should be doing what the Task Switcher does, to prevent these kinds of mismatches, since both are displaying windows, not apps. For the Icons-Only Task Manager, using the app icon makes more sense since it's designed to be listing apps, not windows. On Wayland it's not possible to assign an icon to a window without a desktop file, which means this bug will have to be closed as intentional. I don't follow. How is that relevant, and why can't the non-icons-only Task Manager do the same thing that the Alt+Tab Task Switcher is already doing? If the Task Switcher can do it, surely the Task Manager can also do it, no? Because people who designed the wayland protocol had weird thoughts. That's it. I don't understand what that means, sorry. Can you explain the technical details? |