Bug 417969 - Inability to deterministically choose when an icon should be monochrome and when it should be colorful
Summary: Inability to deterministically choose when an icon should be monochrome and w...
Status: RESOLVED MOVED
Alias: None
Product: Breeze
Classification: Plasma
Component: Icons (show other bugs)
Version: 5.18.1
Platform: Other Linux
: HI normal
Target Milestone: ---
Assignee: visual-design
URL: https://phabricator.kde.org/T10413
Keywords:
: 276101 403512 417879 417920 418006 418009 418093 418095 429135 (view as bug list)
Depends on:
Blocks: 373087
  Show dependency treegraph
 
Reported: 2020-02-21 05:58 UTC by Nate Graham
Modified: 2023-08-07 15:53 UTC (History)
7 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 Nate Graham 2020-02-21 05:58:05 UTC
Breeze icons currently come in two styles: monochrome and colorful.

Generally, the monochrome style is used for small icons: 16px, 22px, and 24px (for compatibility with GTK which uses the 24px size). Colorful icons are generally 32px or larger.

This leads to a general rule: use monochrome for small icons, and color for large icons. This works fine for icons all of whose sizes are in one style or the other.

It stops working so well for icons that have multiple sizes, with small monochrome versions and larger colorful versions, because some of the time we want to use colorful icons for small sizes and some of the time we want to use monochrome icons for large sizes.

For example, we want an app's icon to be colorful for the small 16px version shown in the titlebar, but monochrome if it happens to have a system tray icon (e.g. Plasma Vault). And we want toolbar icons to continue to use the monochrome style at 32px and larger sizes even if they happen to have colorful versions.

Right now we don't really have a way to do this within the confines of a single icon theme.
Comment 1 Nate Graham 2020-02-21 05:58:18 UTC
*** Bug 417920 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2020-02-21 05:58:49 UTC
*** Bug 417879 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2020-02-21 13:25:35 UTC
BTW feel free to keep filing bugs on this issue as you file them Patrick, just mark them as duplicates of this bug. I'd like to use it primary for collecting duplicates so we can get a sense of the impact on users.

The developer discussion is taking place in https://phabricator.kde.org/T10413.
Comment 4 Nate Graham 2020-02-21 16:07:31 UTC
*** Bug 403512 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2020-02-21 16:07:46 UTC
*** Bug 276101 has been marked as a duplicate of this bug. ***
Comment 6 Patrick Silva 2020-02-21 18:50:30 UTC
*** Bug 418006 has been marked as a duplicate of this bug. ***
Comment 7 Patrick Silva 2020-02-21 19:17:59 UTC
*** Bug 418009 has been marked as a duplicate of this bug. ***
Comment 8 Patrick Silva 2020-02-23 14:02:26 UTC
*** Bug 418095 has been marked as a duplicate of this bug. ***
Comment 9 Patrick Silva 2020-02-23 14:02:29 UTC
*** Bug 418093 has been marked as a duplicate of this bug. ***
Comment 10 Dawid Wróbel 2020-05-17 18:45:59 UTC
*** Bug 404959 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2020-05-18 14:47:00 UTC
We are discussing this at https://phabricator.kde.org/T10413.
Comment 12 Nate Graham 2020-11-15 15:07:36 UTC
*** Bug 429135 has been marked as a duplicate of this bug. ***