max / quasi

0.17.0: a field says how much of its row it asked for Settled by Max 2026-08-16 against quasicoherent problem 6d6a9160: fill is determined at the description stage. Column::width has carried this fact about a table cell since the beginning and Share carries it about a region, so a leaf control having no way to say it was an inconsistency in where the line sat rather than a principle being upheld. What found it was audiofiles' toolbar, which kept a measured trailing_width in renderer memory, corrected it a frame late, and needed two constants to survive the first frame -- twenty lines to say Fill. It is an intent and not a measurement, the same division Column makes: the actual floor stays with makeover-geometry. A field carrying pixels would be the thing this replaces. The default is Fill, matching Column::new and matching what every renderer did before the member existed, so a description written yesterday draws the same way today. Content would have read tidier and would have silently narrowed every field in every app on the day it landed, which is the one thing an additive member must not do. quasi-immediate honours it. Fill is egui's own behaviour so it does nothing; Content and Fixed need a number the description does not carry, so the renderer guesses, which is where quasi-tui's table sizing already leaves the same question -- a fallback "until the vocabulary carries a measure". A guess rather than nothing, because Content and Fill drawing identically would make the member unfalsifiable here. quasi-webview says it as data-width on the field's wrapper, for data-tone's reason: a fact the description carried is not a styling hook this renderer invented. quasi-tui does not honour it yet, for the reason its table sizing does not: a terminal wants a measure.