On Mon, Dec 01, 2025 at 01:43:28PM -0800, Per Bothner wrote: > On 12/1/25 13:09, Gavin Smith wrote: > > I see with the current output, the output looks like this: > > > > <div class="nav-panel"> > > <p width="100%"> > > <span class="nav-button">...</span>*</p> > > </div> > > > > where * indicates multiple <span> elements. > > > > In the HTML code you sent you had: > > > > <div class="nav-container"> > > > > in place of: > > > > <p width="100%"> > > > > You then set CSS rules on .nav-container, most importantly "display: flex;". > > > > Would we need to add a "nav-container" class, perhaps on the <p> element? > > Or get rid of the <p> element and change the CSS to use nav-panel/nav-button.
In my testing, getting rid of the <p> element so that span.nav-button was contained directly in div.nav-panel led to less vertical space between the navigation panel and the preceding horizontal rule. This is not important when the manual is split by node, but looks worse when non-split, in my opinion. So I would rather get rid of the <div> element and put the .nav-container class on the <p> element. Another change, implied by your example, is to move the separating comma inside the span.nav-button element.
