| dynamic-available-size-iframe.html |
|
459 |
| min-content-max-content.css |
All classes here intentionally declare height/width/block-size
twice. Just reveals if keyword is supported.
According to the spec, for the sizing properties,
height/min-height/max-height, and width/min-width/max-width,
if specified for the inline axis, use the min-content/max-content inline
size; otherwise behaves as the property’s initial value.
The 'block-size' property (and its max-/min- properties) is just an alias
for height (or width) and accepts the same values. Since it's not
inline-axis, by definition, it always treats the 'min-content' and
'max-content' values as the initial value.
https://drafts.csswg.org/css-sizing/#sizing-values
|
2018 |
| replaced-min-max-1.png |
|
957 |
| replaced-min-max-2.png |
|
1175 |
| replaced-min-max-3.png |
|
1144 |
| replaced-min-max-4.png |
|
1018 |
| replaced-min-max-5.png |
|
1026 |
| replaced-min-max-6.png |
|
1175 |
| replaced-min-max-7.png |
|
1276 |
| replaced-min-max-8.png |
|
1018 |
| replaced-min-max-9.png |
|
1025 |
| replaced-min-max-10.png |
|
1775 |
| replaced-min-max-11.png |
|
1357 |
| replaced-min-max-12.png |
|
1744 |
| replaced-min-max-13.png |
|
1357 |
| replaced-min-max-14.png |
|
1018 |
| replaced-min-max-15.png |
|
1025 |
| replaced-min-max-16.png |
|
1018 |
| replaced-min-max-17.png |
|
1026 |
| replaced-min-max-18.png |
|
1073 |
| replaced-min-max-19.png |
|
1074 |
| replaced-min-max.png |
|
1083 |
