- Shipped
- September 4, 2026 at 7:51 PM UTC
- Author
- Kamo
- Commit
- f40985f
Every other field on the report form is sized by its content. The description is the one somebody is actually writing in, so it now takes whatever height is left — and maximizing the tool window is therefore worth doing. Three parts, and all three are needed: The scroll area gains an inner flex column at `minHeight: 100%`, not `height: 100%`. At a fixed full height a form taller than the window would compress its own fields, because flex children shrink by default. As a minimum it is exactly full height when there is room to spare — which is the room the description takes — and grows past it when there is not, at which point the outer box scrolls and nothing is squashed. The field becomes a flex item with a `minHeight` floor. `minRows` is gone with it: that drives TextareaAutosize, which measures the content and writes an inline height, and with `flex-basis: 0` there would otherwise be nothing stopping the field collapsing to zero. The textarea is released with `height: auto !important`, NOT `height: 100%`. The outlined wrapper stretches its children, so the textarea would fill it unaided — except a flex item with a definite cross-size does not stretch, and autosize gives it one inline. Setting height back to auto restores the stretch instead of fighting it. 100% was tried first and silently does nothing at all: the percentage has no definite containing block to resolve against, so it falls back to auto and the field renders at its intrinsic two rows, with no error anywhere to notice. Measured, not assumed. A puppeteer harness built from this component's own emotion output gives 240px of textarea in a 720px window, 444px at 940px, and a floored field with the form scrolling at 430px — with the title field still 40px in all three. The committed guard asserts the rule rather than the height, since jsdom does no layout, and it was confirmed to fail when the rule is reverted to 100%.