Closed Shatur closed 1 year ago
Not stale.
I believe this should be closed as:
So I believe we should close this as a platform restriction. The new tray icon spec that is in works doesn't have the possibility to set pixmaps, at all, so it's likely that in future we won't have the tray counter at all on Linux, only those monochrome icons with dots in vector format (it's unrealistic to have counter with the XDG icon theme spec as there would have to be thousands of vector icon files, for each count). The API allows to set absolute path to a raster icon, but that won't be friendly to HiDPI unlike the IconPixmap array in the existing spec, so is not really usable. Setting absolute path to a raster icon usually leads to incompatibility with HiDPI (if e.g. 22px icon is passed) or various tray host bugs, e.g. not downscaling the icon, so it's out of bounds or cropped (that's how e.g. Ubuntu/Ayatana indicators behave right now, they have only the ability to use XDG icon theme spec or pass a path to a raster file, like the new spec). Unfortunately, that's where the Linux stack goes, with the leadership of GNOME and its HIG.
Anyone can contribute an option to disable monochrome icon still, though, if that's something acceptable to anyone, even after this is issue is closed (as I already said, no guarantee it would be merged though, it's not up to me).
Is your feature request related to a problem?
After version 2.5.5, if the system theme contains a monochrome icon, then the notification counter is not displayed on it.
Before:
After:
This approach may be look nice in some situations, but it is much less practical.
Describe the solution you'd like
It would be nice to add an option that would return the old behavior (displaying notification counter). It would make everyone happy.
As a workaround, users can change the icon theme for Telegram, which does not contain the icon for the system tray. But then the Telegram icon will look different from the rest of the monochrome icons (see how it worked before in the screenshots above).
Additional context
I talked with @ilya-fedin and he said that I should ask @john-preston.
Related issues reported by confused users: #10264, #10251, #10263.