What "Weak Declaration" Means for aspect-ratio
With aspect-ratio now flagged on in both Firefox and Safari, broad cross-browser support looks close, and the property behaves largely as its name suggests. PPK's write-up gives the useful framing here: he calls it a weak declaration. That isn't an official term, but it captures how the property loses every conflict.
When the Ratio Holds
Each of these produces a 16 / 9 element:
.movie-card {
aspect-ratio: 16 / 9;
}
.movie-card {
width: 50%;
aspect-ratio: 16 / 9;
}
When It Loses
This one does not:
.movie-card {
width: 150px;
height: 150px;
aspect-ratio: 16 / 9;
}
An explicit width or height wins, so the ratio is simply not applied. The declaration is weak because it never overrides a dimension set by any other means — and the same applies beyond width and height. A max-height that kicks in will be respected, meaning the element can follow the aspect ratio in some conditions and still drop it whenever a max-* value forces a break.
Content Also Breaks It
The weakness extends to markup inside the box. If the element's height is constrained only by aspect-ratio and it holds a lot of text, the constraint doesn't hold: the content expands the element.
This behavior is a sensible default, since it avoids unwanted side effects. Where a ratio must be enforced on a box with content, the padding trick remains available — the safe approaches to it still work — and aspect-ratio is simply a much nicer syntax for jobs the trick used to handle.
Layout Context Gotchas
PPK's article also details how the property behaves inside flexbox and grid, where there are real gotchas. Setting align-content: stretch; is one example of something that can break an aspect ratio — weak declaration, again.



