off css classes #8865

New issue

Open

opened 2026-05-23 03:54:46 +01:00 by JakeStanger · 4 comments

JakeStanger commented

2026-05-23 03:54:46 +01:00

Owner

Originally created by @Kommynct on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1434

Is your feature request related to a problem? Please describe.
I just want to be able to have different colors for when something is muted/off/at a different level

Describe the solution you'd like
a css class, like waybar has: ex

#pulseaudio.muted
#idle_inhibitor.deactivated
#network.disconnected

that way I can grey them out

Originally created by @Kommynct on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1434 **Is your feature request related to a problem? Please describe.** I just want to be able to have different colors for when something is muted/off/at a different level **Describe the solution you'd like** a css class, like waybar has: ex #pulseaudio.muted #idle_inhibitor.deactivated #network.disconnected that way I can grey them out

JakeStanger added the

labels

2026-05-23 03:54:46 +01:00

JakeStanger commented

2026-05-23 03:54:47 +01:00

Author

Owner

@JakeStanger commented on GitHub (Mar 30, 2026):

This is (partially) possible already (on master). The profiles system is primarily for allowing you to configure modules differently at different levels, but each profile also attaches a class name allowing you to style the module depending on its state.

https://github.com/JakeStanger/ironbar/wiki/profiles

Volume, battery and network manager support the system so far.

@JakeStanger commented on GitHub (Mar 30, 2026): This is (partially) possible already (on master). The profiles system is primarily for allowing you to configure modules differently at different levels, but each profile also attaches a class name allowing you to style the module depending on its state. https://github.com/JakeStanger/ironbar/wiki/profiles Volume, battery and network manager support the system so far.

JakeStanger commented

2026-05-23 03:54:47 +01:00

Author

Owner

@Kommynct commented on GitHub (May 17, 2026):

Should this be closed after the release? Anything left?

@Kommynct commented on GitHub (May 17, 2026): Should this be closed after the release? Anything left?

JakeStanger commented

2026-05-23 03:54:47 +01:00

Author

Owner

@JakeStanger commented on GitHub (May 17, 2026):

I don't think your initial request is fully resolved. If you think it is though I'm happy to close

@JakeStanger commented on GitHub (May 17, 2026): I don't think your initial request is fully resolved. If you think it is though I'm happy to close

JakeStanger commented

2026-05-23 03:54:47 +01:00

Author

Owner

@Kommynct commented on GitHub (May 17, 2026):

I don't think your initial request is fully resolved. If you think it is though I'm happy to close

Sorry I haven't really looked into how exactly the profiles work, we're still missing disabled/disconnection distinction, I think, so yeah it does stay open, thank you so much for the work though!

@Kommynct commented on GitHub (May 17, 2026): > I don't think your initial request is fully resolved. If you think it is though I'm happy to close Sorry I haven't really looked into how exactly the profiles work, we're still missing disabled/disconnection distinction, I think, so yeah it does stay open, thank you so much for the work though!