Jamie, I cannot offer answers to most of your questions, but I can offer a suggestion on your proposed approach to fixing this issue.
On Wed, Jul 22, 2026 at 11:36 AM Jamie Fitzgerald <[email protected]> wrote: > A few things might make that easier to control. > > First, because the behavior would be opt-in, the first patch could be > limited to the new API, FixedText, and maybe VclBox. During testing, the > second layout pass could also be placed behind a runtime flag so the > current and new behavior are easy to compare. > My suggestion is to separate the three elements you've mentioned here (the new API, FixedText, and VclBox) into separate patches. That way you can better ensure that each change won't break anything. I believe there are automated tests for (some aspects of) the UI; it might be worth seeing if any of them cover the elements you'd be changing, and maybe even write some tests if appropriate (this could be another patch before the new API) to ensure that existing behavior doesn't change. > Jamie Fitzgerald > > [email protected] > Ben Urban
