Inspect the working example
The second track uses minmax(0,1fr). Both paragraphs permit wrapping anywhere, retaining the long filename instead of clipping it.
| Case | Input or inspection | Result and meaning |
|---|---|---|
| Label track | Read first track width | 80px |
| Content track | 260−80−10 | 170px |
| Token | Inspect retained text and overflow | Full text wraps within its track |
Follow the browser mechanism
A bare 1fr track has an automatic minimum that can be influenced by intrinsic content. minmax(0,1fr) supplies an explicit zero minimum; wrapping handles the text itself. This lesson measures track sizing, not an invoice association or a stock layout choice.
A bare fractional track can inherit a large minimum
The alternative restores 1fr and disables emergency wrapping.
<style>body{margin:8px}</style>
<style>.grid{display:grid;width:260px;grid-template-columns:80px 1fr;gap:10px}.grid p{margin:0;overflow-wrap:normal}</style><section class="grid"><p>Filename</p><p>very_long_workshop_source_file_without_spaces.html</p></section>The unbroken filename expands the second track beyond its intended share and overflows the 260px grid.
Try the repair
Does a zero track minimum by itself guarantee that an unbroken string is readable inside the smaller track?
Show the worked answer
No. It permits the track to shrink; the text still needs an appropriate wrapping or other explicit presentation rule.
- Read computed track widths and measure the actual children.
- Check both sizing and retained text.