From 7f52e94d2386858cb32c18d5a5982dbb966cb174 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Tue, 15 Sep 2026 17:19:40 +0200 Subject: fix: stop the launcher hover from erasing its own mark The mark is filled with @main-bg so it contrasts against the accent pill, and the hover rule set that pill's background to @main-bg. Identical colours, so hovering painted the mark in its own colour and the pill went blank. This is the same fault as the first version, one state over: that one filled the mark with @accent and drew it on the @accent pill. The mark is a rendered image inside the module rather than a CSS background, so CSS cannot recolour it per state, and any hover colour would have to contrast with both @accent and @main-bg at once. So the pill holds its colour: it is dropped from the shared hover rule and its own override is gone, leaving the cursor to signal that it is clickable. Both stylesheets carry a comment saying why, because the obvious edit is to add a hover back. Co-Authored-By: Claude Opus 5 --- styles/pills.css | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'styles/pills.css') diff --git a/styles/pills.css b/styles/pills.css index 93a8855..1794523 100644 --- a/styles/pills.css +++ b/styles/pills.css @@ -34,7 +34,9 @@ /* Hover. The one rule that makes the bar feel alive, and the reason every * pill declares a transition above. */ -#image.launcher:hover, +/* The launcher is absent on purpose: its mark is an image CSS cannot recolour, + * so a hover background would paint the mark in its own colour. See + * modules.css. */ #clock.date:hover, #clock.time:hover, #custom-vmdot:hover, -- cgit v1.2.3