From b08143f5ac57c1ba2c5730a2657c0573c514f9a0 Mon Sep 17 00:00:00 2001 From: Martin Mattel Date: Tue, 15 Sep 2026 16:45:27 +0200 Subject: [PATCH] fix: more tabs.css fixes --- ui/supplemental/css/tabs.css | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/ui/supplemental/css/tabs.css b/ui/supplemental/css/tabs.css index a481680..8621bca 100644 --- a/ui/supplemental/css/tabs.css +++ b/ui/supplemental/css/tabs.css @@ -54,7 +54,16 @@ margin-top: 0; } +/* `margin-top` is repeated here on purpose. The canonical `.tabs li + li` rule + * above (0,1,2) is outspecified by the stock Antora default UI's + * `.doc .ulist li+li { margin-top: .5rem }` (0,2,2), so on its own it never + * takes effect: every chip but the first kept a 0.5rem top margin and the strip + * rendered with the first chip sitting ~9.6px above the others (only visible on + * tabsets with more than one tab -- the single-tab service pages never showed + * it). This selector ties that specificity and, as tabs.css loads after + * site.css (see partials/head-styles.hbs), wins on source order. */ .tabs.ulist li + li { + margin-top: 0; margin-left: 0.25em; }