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
Box in context of the layout API is just being used as input to the layout algorithm.
They are "something that has an associated computed style". In this context they have no layout information themselves. (Fragments have that in this context).
This may be confusing to folks from CSS specs / authors who think of a box having layout information.
¯_(ツ)_/¯
The text was updated successfully, but these errors were encountered:
The CSS terminology used to be a lot more vague, and throw the words box or element around without much consideration, but I think that in the more modern and deliberate usage, the distinction between Box and Fragment does match the way these words are used in the spec. (even though in contexts where we don't care about fragmentation, I am pretty sure we still occasionally use box when we mean box fragment.)
Yeah, a box knows what its display type is and has fully resolved computed styles, but it doesn't have layout information - it generates fragments which do have size/position. Boxes are abstract style/content containers, is all.
Box
in context of the layout API is just being used as input to the layout algorithm.They are "something that has an associated computed style". In this context they have no layout information themselves. (Fragments have that in this context).
This may be confusing to folks from CSS specs / authors who think of a box having layout information.
¯_(ツ)_/¯
The text was updated successfully, but these errors were encountered: