The comparison functions take full math expressions with mixed units:
min(a, b, …)is the smallest value, so it sets a maximum:width: min(100%, 60rem)is full width until 60rem, replacingwidth+max-width.max(a, b, …)is the largest, so it sets a minimum:padding: max(1rem, 3vw).clamp(MIN, VAL, MAX)is exactlymax(MIN, min(VAL, MAX)): the preferred value, held between the bounds. IfMINis greater thanMAX,MINwins.
Fluid typography uses a viewport-relative preferred value: font-size: clamp(1rem, 1rem + 1vw, 3rem) grows smoothly with the window instead of jumping at breakpoints. Container units (cqi) do the same per component.
The zoom catch. Browser zoom enlarges CSS pixels, so a zoomed window has fewer CSS pixels across. A vw value shrinks in CSS pixels by exactly as much as zoom enlarges each pixel; on screen it stays the same size. A heading at 2.5vw stayed 30 device pixels at (emulated) 100%, 200% and 300% zoom, and ignored the user's default font size too. WCAG 2.2 SC 1.4.4 requires text to be resizable to 200%; failure F94 is text sized mainly with viewport units.
The fix is to give rem part of the preferred value, because only the rem part scales. At zoom z, rendered size is z × rem part + vw part, so it doubles once (z − 2) × rem part ≥ vw part. Keep the vw coefficient small and the bounds in rem: bounds scale fully with zoom and with the default font size. WCAG's Understanding document allows reaching 200% at a higher zoom level: its example halves the font size at 400% zoom and still counts the text as twice as large.