min-width and min-height start as auto. On ordinary blocks that means 0, but flex and grid items get an automatic minimum size: their content-based minimum size, essentially the min-content size (the longest word, the widest image or fixed-width child).
The layout algorithms clamp items to their minimum sizes. A flex: 1 item therefore stops shrinking at its content's min-content width and overflows the container. Symptoms: text-overflow: ellipsis never appears, a long URL or <pre> pushes a column wider, a nested scroll panel grows instead of scrolling.
Flexbox (§4.5) applies it in the main axis to items that aren't scroll containers. The content-based minimum is the min-content size, capped by the item's width (or height) when that is definite, and by its max size. So a width: 100px item can shrink to 100px but not further.
Grid (§6.6) applies it only when the item spans a track whose minimum sizing function is auto: auto tracks and 1fr, which means minmax(auto, 1fr). Fixed tracks don't enforce it.
Fixes, most targeted first:
min-width: 0on the item (min-height: 0in a column) opts out explicitly.overflow: hidden | auto | scroll: scroll containers have a zero automatic minimum, and you probably wanted the clipping or scrolling anyway.overflow: clipdoesn't count: it isn't a scroll container.minmax(0, 1fr)in grid sets the track's minimum to zero, so items in it no longer force it open.
The default exists so content doesn't overlap or spill by surprise. For main content areas, the spec suggests a deliberate font-relative minimum such as min-width: 12em over the content-based one.