Wednesday, September 13, 2023
HomeCSSreceptive style - Why does container-type: inline-size (for container questions) appear to...

receptive style – Why does container-type: inline-size (for container questions) appear to damage CSS grid’s minmax( min-content, max-content)?


I have actually obtained a CSS format that trusts CSS grid’s minmax( min-content, max-content) for responsively setting out a lot of its components. Right here’s a lowered instance:

 html, body {margin: 0; cushioning: 0;}
area {
screen: grid;
grid-template-columns: minmax( min-content, max-content) 1fr;
inline-size: 100dvi;
block-size: 100dvb;
history: cream color;
}
short article {
history: lavenderblush;
resize: horizontal;
overflow-x: automobile;
max-inline-size: max-content;
min-inline-size: min-content;
}
apart {
history: lightcyan;
} 
<< area>>.
<< short article>>.
<< p>> This is some message that is long sufficient to cover. Resize me!<.
<.
<< apart>>.
Apart.
<.
<

I would certainly likewise such as to make my UI widgets in those components receptive to just how much area they have readily available. Nonetheless, when I make use of container-type: inline-size to an aspect that is sized as minmax( min-content, max-content) (or perhaps any one of its youngsters), the receptive sizing breaks and also the materials of the component obtain removed. Right here's a lowered instance where you can toggle the actions using a switch:

 html, body {margin: 0; cushioning: 0;}
area {
screen: grid;
grid-template-columns: minmax( min-content, max-content) 1fr;
inline-size: 100dvi;
block-size: 100dvb;
history: cream color;
}
short article {
history: lavenderblush;.
resize: horizontal;.
overflow-x: automobile;.
max-inline-size: max-content;.
min-inline-size: min-content;.
}
article.container {
container-type: inline-size;.
}
apart {
history: lightcyan;.
} 
<< area>>.
<< short article>>.
<< p>> This is some message that is long sufficient to cover. Resize me!<.
<< switch onclick=" this.parentNode.classList.toggle(' container')">> Toggle Container<.
<.
<< apart>>.
Apart
<.
<
  1. Why does this occur?
  2. Just how can I attain a design that is receptive to components' innate dimension, yet with container-width-adaptive widgets, without causing this actions?
RELATED ARTICLES

Most Popular

Recent Comments