On Wed, Oct 7, 2026 at 12:08 PM Branko Čibej <[email protected]> wrote:
> On 7. 10. 2026 16:12, Daniel Sahlberg wrote: > > Den ons 7 okt. 2026 kl 16:05 skrev Evgeny Kotkov via > dev<[email protected]> <[email protected]>: > > Hi all, > > While skimming the latest version of the 1.15 release notes [1], I almost > missed the new "Build System Comparison" table because it is collapsed > inside a <details> element. > > I'd like to propose dropping the <details> and showing the table inline, > for a few reasons: > > - This collapsed content is easy to miss entirely, because the summary line > doesn't look like something clickable with the default styling. > > - I think that the table looks great and enhances the release notes, so we > should not hide it. > > - The current "Build System Comparison > Build System Comparison" hierarchy > reads oddly. > > - I think the release notes aren't long enough to justify collapsing sections. > > Would there be any objections to me committing an ad-hoc patch that removes > the <details> block for this table? > > I'm fine with either approach. There was a wish to keep the notes a > bit shorter (see quoted text in [2]) but it adds 10% to something > people would probably not print either way. > > > > My main gripe about that collapsed table is that it's so amazingly subtle > that no-one who doesn't know its there will find it. The default styling is > moderately horrible, using one little widget that no-one will notice is a > great example of a UI hiding functionality in plain sight. > > So it's either: remove the <detail> wrapper or fix the styling. I could > have a go at the latter, I see it as behaving similarly to a link. > > -- Brane > I'm +1 to remove it and make the table always visible, but if you think a properly styled detail tag will have other uses throughout the site, feel free to experiment with it. I experimented a bit back when it was added (possibly by me?) and just got frustrated with it and gave up. Currently AFAIK it is used in only this one place, so it's only worth messing with it if we want to use it elsewhere too. Thanks, Nathan
