Separate setting for tray background color

[KamilBaczkowski]

I'm submitting a…

[ ] Bug
[x] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

Currently, background color of tray icons is being taken from the background setting in the bar section. This is fine, but doesn't allow for fine-tuning your config very well; if you want to use different bar colors for focused and unfocused outputs, then you're stuck with tray icons that use a background color that doesn't really fit in.

Desired Behavior

I would introduce a new setting called tray_background that, if set, would dictate the background color of the tray icons. If it wasn't set, the value of background would be used as a fallback.

Impact

[x] This feature requires new configuration and/or commands

Environment

Output of i3 --moreversion 2>&-:

Binary i3 version:  4.19.1 (2021-02-01) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.19.1 (2021-02-01) (pid 1348)

- Linux Distribution & Version: Updated Manjaro Linux
- Are you using a compositor (e.g., xcompmgr or compton): yes, picom

[i3bot]

Please note that new features which require additional configuration will usually not be considered. We are happy with the feature set of i3 and want to focus in fixing bugs instead. We do accept feature requests, however, and will evaluate whether the added benefit (clearly) outweighs the complexity it adds to i3.

Keep in mind that i3 provides a powerful way to interact with it through its IPC interface: https://i3wm.org/docs/ipc.html.

[Airblader]

I think rather we should consider it a bug that the tray background isn't taken from the focused_background color if provided + focused. Then this would be solved without additional configuration.

[KamilBaczkowski]

That would also be nice

[hakoerber]

I think rather we should consider it a bug that the tray background isn't taken from the focused_background color if provided + focused. Then this would be solved without additional configuration.

Just stumbled upon this exact problem. I could not find a separate issue for that, though. Can you point me to it? If there is none, I will open a new issue to track this problem separately.

[Airblader]

I think we can just use this issue for that.