You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[css-display] Must a non-box-generated containing block be the initial containing block? #1672
a containing block is not a box (it is a rectangle), however it is often derived from the dimensions of a box. If properties of a containing block are referenced, they reference the values on the box that generated the containing block. (For the initial containing block, the values are taken from the root element.)
But what if something references a property of a containing block that has not been generated by any box, and is not the initial containing block?
According to CSS 2 and CSS Position, I think this case is not possible, but then you should say so. Otherwise, if it's possible, define what should happen.
As far as I know, nothing needed to be clarified - other than the ICB, every containing block is generated by a box, so any question about CBs that aren't generated by boxes (other than the ICB) is moot.
I'm not sure we need to preclude the possibility in the future--though I don't see us doing it in the future, I don't think we gain anything by locking down the definition here, either. So I think it's fine to leave the definition as-is, and if we end up with more cases like the ICB, define how they work when we create them.
Activity
tabatkins commentedon Aug 3, 2017
Other than the ICB, containing blocks are always generated by a box.
Loirooriol commentedon Dec 8, 2017
@tabatkins This has not been clarified in CSS Display, and one can't trust CSS Position because it's not maintained. So this issue is not fixed.
tabatkins commentedon Dec 9, 2017
As far as I know, nothing needed to be clarified - other than the ICB, every containing block is generated by a box, so any question about CBs that aren't generated by boxes (other than the ICB) is moot.
But yeah, one can't trust Position.
Loirooriol commentedon Dec 9, 2017
It's this statement what I think is not clear. It would be useful to include it in the definition.
fantasai commentedon Mar 20, 2018
I'm not sure we need to preclude the possibility in the future--though I don't see us doing it in the future, I don't think we gain anything by locking down the definition here, either. So I think it's fine to leave the definition as-is, and if we end up with more cases like the ICB, define how they work when we create them.